Bug 86843 - crash after stop build pressed
Summary: crash after stop build pressed
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.4
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-09 13:26 UTC by Lukasz Michalski
Modified: 2005-04-14 12:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
gdb stderr log and backtrace (20.83 KB, text/plain)
2004-08-09 13:33 UTC, Lukasz Michalski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz Michalski 2004-08-09 13:26:42 UTC
Version:           3.0.4 (using KDE KDE 3.2.3)
Installed from:    Compiled From Sources
Compiler:          gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pld-linux/3.3.4/specs
Configured with: ../configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --infodir=/usr/share/info --mandir=/usr/share/man --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-languages=c,c++,f77,objc,ada,java,ksi --enable-c99 --enable-long-long --enable-multilib --enable-nls --with-gnu-as --with-gnu-ld --with-system-zlib --with-slibdir=/lib --without-x i686-pld-linux
Thread model: posix
gcc version 3.3.4 (PLD Linux)
 compiled against qt-3.3.2
OS:                Linux

"Stop build" button is not working and KDeveleop is terminating my X server. 
It happens when:
 - build is in progress and i try to stop it using stop button. make process 
is not terminated and after some while X server exists.
 - build is in progress and i try to stop it typing "killall make" into xterm. 
X server terminates imedietly.

Id does not happen when build is in progress and I exit KDevelop using 
File->Quit

I am using kdevelop 3.0.4 and KDE 3.2.3, XFree86 4.0.4, nvidia GeForce card.

I tried both nv.o driver from XFree distribution and nvidia.ko kernel module. 
Both give the same results.

I switched to from XFree86 to X11 and bugs still exists.

I discovered that when I run kdevelop from console, then this stop button only crashes 
kdevelop without termionating my XServer

I attached backtrace from sample gdb session.
Comment 1 Lukasz Michalski 2004-08-09 13:33:40 UTC
Created attachment 7048 [details]
gdb stderr log and backtrace
Comment 2 Lukasz Michalski 2004-08-09 13:34:52 UTC
Forgot to metion: this bug still exists in kdevelop 3.0.95 (compiled from sources)
Comment 3 Jens Dagerbo 2004-08-09 14:29:12 UTC
Please reconfigure/rebuild with --enable-debug=full and see if you can get a better backtrace. AFAIK, you're the only one who has managed to trigger this and unless there is something concrete to go on I'm most inclined to write this off as flakey hardware.

Some questions: 
1. Are you running KDevelop from within KDE? Is it started from the K-menu?
2. Does the same problem appear if you run KDevelop from konsole?
Comment 4 Lukasz Michalski 2004-08-09 16:43:22 UTC
I recompiled with debug symbols 3.0.95 and tried my another project:


EPORT=\"\" -DPACKAGE=\"common\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1  -I. -I/home/users/zork/sources/common/common     -O0 -g3 -MT tm.o -MD -MP -MF ".deps/tm.Tpo" -c -o tm.o /home/users/zork/sources/common/common/tm.cpp; \
kdevelop (output views): Directory filter line then mv -f ".deps/tm.Tpo" ".deps/tm.Po"; else rm -f ".deps/tm.Tpo"; exit 1; fi
kdevelop (output views): Found: compiling tm.cpp(g++)
kdevelop (output views): Directory filter line if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"common\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1  -I. -I/home/users/zork/sources/common/common     -O0 -g3 -MT sem.o -MD -MP -MF ".deps/sem.Tpo" -c -o sem.o /home/users/zork/sources/common/common/sem.cpp; \
kdevelop (output views): Directory filter line then mv -f ".deps/sem.Tpo" ".deps/sem.Po"; else rm -f ".deps/sem.Tpo"; exit 1; fi
kdevelop (output views): Found: compiling sem.cpp(g++)
kdevelop (output views): Directory filter line if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"common\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1  -I. -I/home/users/zork/sources/common/common     -O0 -g3 -MT staticspace.o -MD -MP -MF ".deps/staticspace.Tpo" -c -o staticspace.o /home/users/zork/sources/common/common/staticspace.cpp; \
kdevelop (output views): Directory filter line then mv -f ".deps/staticspace.Tpo" ".deps/staticspace.Po"; else rm -f ".deps/staticspace.Tpo"; exit 1; fi
kdevelop (output views): Found: compiling staticspace.cpp(g++)
kdevelop (output views): Directory filter line if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"common\" -DVERSION=\"0.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1  -I. -I/home/users/zork/sources/common/common     -O0 -g3 -MT treeutils.o -MD -MP -MF ".deps/treeutils.Tpo" -c -o treeutils.o /home/users/zork/sources/common/common/treeutils.cpp; \
kdevelop (output views): Directory filter line then mv -f ".deps/treeutils.Tpo" ".deps/treeutils.Po"; else rm -f ".deps/treeutils.Tpo"; exit 1; fi
kdevelop (output views): Found: compiling treeutils.cpp(g++)
kdevelop (output views): Directory filter line rm -f libcommon.a
kdevelop (output views): Directory filter line ar cru libcommon.a pointers.o conversion.o exception.o bitmask.o autoincrementedmap.o observer.o membertree.o tm.o sem.o staticspace.o treeutils.o
kdevelop (output views): Directory filter line ranlib libcommon.a
kdevelop (output views): Directory filter line make[1]: Leaving directory `/home/users/zork/sources/common/debug/common'
kdevelop (output views): Directory filter line make[1]: Entering directory `/home/users/zork/sources/common/debug'
kdevelop (output views): Directory filter line make[1]: Nothing to be done for `all-am'.
kdevelop (output views): Directory filter line make[1]: Leaving directory `/home/users/zork/sources/common/debug'

Program received signal SIGTERM, Terminated.
0x418f9a31 in select () from /lib/libc.so.6
(gdb) bt
#0  0x418f9a31 in select () from /lib/libc.so.6
#1  0x415e07d4 in ?? () from /usr/lib/libqt-mt.so.3
#2  0x00000015 in ?? ()
#3  0x4116d908 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#4  0x4116d7b8 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#5  0x4115c4c1 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#6  0x080c5a32 in main (argc=1, argv=0xbffff9d4) at main.cpp:132
(gdb) quit
The program is running.  Exit anyway? (y or n) y

Now I am trying to recompile qt using specs from my distribution.

I got this behaviour on two identical machines with two identical linuxes (PLD 2.0 beta) installed. On both "stop" button is useless.

Answers:.
1. I am using kdevelop from within KDE. If it is started from K-menu then "stop" terminates my X-Server. I have no other problems with any KDE-app installed in my system.

2. If kdevelop is started from console then it just prints "terminated" after "stop" button is used.

Comment 5 Lukasz Michalski 2004-08-10 10:12:14 UTC
QT rebuild didn't help :(

What else can I do?

I tried to debug kevelop 3.0.92 but I am little bit lost in the sources.....

Comment 6 Jens Dagerbo 2005-01-08 03:52:48 UTC
There is still no one else who has reproduced this problem. I have never heard of "PLD Linux" but maybe they enforce some non-standard process policy or something...

There has been a slight change in the relevant code in HEAD recently, unless that happens to help, I can't see that we can do anything about this.

Closing as WONTFIX.
Comment 7 Lukasz Michalski 2005-04-14 12:07:04 UTC
Problem disappeared between 3.1.2 and 3.2.0

Regards,
Łukasz