Community
Participate
Working Groups
Build ID: M20080221-1800 Steps To Reproduce: 1. While debugging (program may be in run mode or in stopped, bug seems not related to debugged program state), add a breakpoint, which leads to warning marker (yellow one) with "- Unresolved Breakpoint" tooltip text Then, wait some seconds, eclipse crash. Or, continue execution of program, eclipse crash. Don't exactly understood when crash, seems somehow random and not connected with debugged program execution. No log messages in .log file. Debugged program continues execution correctly, only eclipse crashes. Crash is simply like eclipse closing all windows and disappearing, no error boxes or likely. More information: Windows XP Service pack 2. Eclipse v3.3.2 Mingw 3.4.2 gdb 6.6 cdt 4.0.3 qt eclipse integration 1.0.1 subclipse 1.2.4
Can you run it from console and check what is printed there? Should be jvm crash dump. Can you reproduce it easily? If you disable subclipse plugin would it still crash?
I tried disabling subclipse, still crash. To me seems reproducible, I just need to add a breakpoint that leads to the yellow sign "unresolved breakpoint" to have a crash. Don't exactly know how breakpoint can be resolved or unresolved, some lines in a func usually lead to unresolved. How do I run eclipse from console? I mean without having it opening it's own console; if I run from command line all eclipse debug output does not go on the console where I launch it from, but on it's own console, which closes when crashes then cannot be read (I tried to arrange windows in a way to see both when crash, but it's really the same moment, no time to read anything).
windows version has eclipsec.exe executable or something like this... Run it with -consolelog option We really need this crash log, because it native library crashing and without it is there is no way anybody can even identify which component it belongs (but it is not CDT for sure)
Created attachment 93944 [details] error log type "BufferBlob"
Created attachment 93945 [details] error log type "Spawner"
Created attachment 93946 [details] error log type "Spawner" (another example, a bit different trace)
I found the "eclipsec.exe" thing, anyway in my eclipse directory there were many "hs_err_pidXXX.log" files. I divided them mainly in 2 categories, those caused by class "BufferBlob" and those caused by class "org.eclipse.cdt.utils.spawner.Spawner". As a chronological note I see that new ones are mainly caused by "BufferBlob", the newest caused by "Spawner" is dated 14/03/2008 (I do not use eclipse daily anyway, then this date may be not too precise). I have many more, all quite similar anyway, if you wish I can send them too.
Created attachment 95535 [details] error log type "Spawner", jvm v1.5.0_15
Hi! I did some more test, with precedent jvm to see if problem was java6 usage. The bug is still there with java5 update 15, backtrace is like other ones. I've seen that the "BufferBlob" kind of traces begun when I installed java6 update 5; with java6 update 3 stack trace was of the "Spawner" kind.
screenshot from windbg debugger
Created attachment 95665 [details] screenshot from windbg of the usual crash in eclipse debugging
