Author Topic: debugger crashes  (Read 5409 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5187
debugger crashes
« on: January 14, 2006, 03:42:48 pm »
rev 1754
rpt :
-------------------

Error occured on Saturday, January 14, 2006 at 15:40:51.

D:\work\cb_snap\src\output\codeblocks.exe caused an Access Violation at location 68f87191 in module D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll Reading from location fffffff8.

Registers:
eax=fffffff4 ebx=00bb5cc0 ecx=00000001 edx=00000001 esi=68fc8690 edi=0188f060
eip=68f87191 esp=0022f620 ebp=0022f628 iopl=0         nv up ei ng nz ac pe cy
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010293

Call stack:
68F87191  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F87191  _ZN8cbPlugin9OnReleaseEb
68F871B5  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F871B5  _ZN8cbPlugin9OnReleaseEb
68F87A91  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F87A91  _ZNK8cbPlugin7GetTypeEv
68F8148D  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F8148D  _ZN16cbDebuggerPluginD1Ev
68F677C7  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F677C7  PluginSDKVersion
68F544FB  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F544FB  PluginSDKVersion
68F560A9  D:\work\cb_snap\src\output\share\codeblocks\plugins\debuggergdb.dll:68F560A9  PluginSDKVersion
100AA0E8  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AA0E8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
100AA4AC  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AA4AC  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
100AB489  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AB489  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB2C6  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AB2C6  _ZN12wxEvtHandler20ProcessPendingEventsEv
10001C94  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:10001C94  _ZN12wxAppConsole20ProcessPendingEventsEv
10184E95  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:10184E95  _ZN9wxAppBase6OnIdleER11wxIdleEvent
100CBA68  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100CBA68  _ZN5wxApp6OnIdleER11wxIdleEvent
100AA0E8  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AA0E8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
100AA4AC  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AA4AC  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
100AB489  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100AB489  _ZN12wxEvtHandler12ProcessEventER7wxEvent
10184D37  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:10184D37  _ZN9wxAppBase11ProcessIdleEv
100EC43B  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100EC43B  _ZN11wxEventLoop3RunEv
1018492E  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:1018492E  _ZN9wxAppBase8MainLoopEv
00404CDA  D:\work\cb_snap\src\output\codeblocks.exe:00404CDA
10043817  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:10043817  _Z14wxUninitializev
100B33BA  D:\work\cb_snap\src\output\wxmsw26u_gcc_cb.dll:100B33BA  _Z7wxEntryP11HINSTANCE__S0_Pci
004014DA  D:\work\cb_snap\src\output\codeblocks.exe:004014DA
00459B2A  D:\work\cb_snap\src\output\codeblocks.exe:00459B2A
00401237  D:\work\cb_snap\src\output\codeblocks.exe:00401237
00401288  D:\work\cb_snap\src\output\codeblocks.exe:00401288
7C816D4F  C:\WINDOWS\system32\kernel32.dll:7C816D4F  RegisterWaitForInputIdle



I have to say, the debugger crashes very often. :-(

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5187
Re: debugger crashes
« Reply #1 on: January 14, 2006, 04:21:54 pm »
and once I put a breakpoint it is very hard to get rid of it (almost impossible), I remember other people have also suffered from it.

Clicking in the gutter, removing through breakpoint window -> no luck at all

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: debugger crashes
« Reply #2 on: January 14, 2006, 04:34:59 pm »
Quote
I have to say, the debugger crashes very often.

If only you could give some info like what you were doing when it crashed...

Also, try to post a backtrace by running devel/codeblocks.exe. I don't have the symbols of your build to decode the above...
Be patient!
This bug will be fixed soon...

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5187
Re: debugger crashes
« Reply #3 on: January 14, 2006, 05:13:29 pm »
Yiannis,
I was indeed running from output .... to debug the devel version ;-)

Offline 280Z28

  • Regular
  • ***
  • Posts: 397
  • *insert unicode here*
Re: debugger crashes
« Reply #4 on: January 17, 2006, 04:47:59 am »
I just got a crash, see attached.

[attachment deleted by admin]
78 280Z, "a few bolt-ons" - [email protected]
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
 Check out The Sam Zone :cool:

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: debugger crashes
« Reply #5 on: January 17, 2006, 08:41:52 am »
I just got a crash, see attached.

It would help if you told us what you were doing when it happened...
Be patient!
This bug will be fixed soon...

Offline 280Z28

  • Regular
  • ***
  • Posts: 397
  • *insert unicode here*
Re: debugger crashes
« Reply #6 on: January 17, 2006, 09:29:57 am »
I just got a crash, see attached.

It would help if you told us what you were doing when it happened...

I'm actually not sure :(
78 280Z, "a few bolt-ons" - [email protected]
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
 Check out The Sam Zone :cool:

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Yiannis: Take a closer look at the report :)
« Reply #7 on: January 17, 2006, 05:23:10 pm »
C:\Program Files\CodeBlocks\codeblocks.exe caused an Access Violation at location 68f4a90e in module C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll Reading from location 00000000.

It's a null pointer, those are easy to fix! :)
D:/Devel/codeblocks/src/plugins/debuggergdb/debuggerdriver.cpp:85

Perhaps we need to check out for this == NULL? (I don't see any pointers there)

Edit: OUCH!!! This looks just like a stack overflow!

Code: [Select]
61850270  C:\Program Files\CodeBlocks\codeblocks.dll:61850270  Manager::ProcessPendingEvents()  D:/Devel/codeblocks/src/sdk/manager.cpp:90
6185577A  C:\Program Files\CodeBlocks\codeblocks.dll:6185577A  MessageManager::Log(int, wchar_t const*, ...)  D:/Devel/codeblocks/src/sdk/messagemanager.cpp:257
68F4E850  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F4E850  DebuggerGDB::DebugLog(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:436
68F675AB  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F675AB  GDB_driver::ParseOutput(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/gdb_driver.cpp:213
68F544FB  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F544FB  DebuggerGDB::ParseOutput(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:1174
68F560A9  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F560A9  DebuggerGDB::OnGDBOutput(wxCommandEvent&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:1428
100AA0E8  C:\Program Files\CodeBlocks\wxmsw26u_gcc_custom.dll:100AA0E8  _ZN12wxEvtHandler21ProcessEventIfMatchesERK21wxEventTableEntryBasePS_R7wxEvent
100AA4AC  C:\Program Files\CodeBlocks\wxmsw26u_gcc_custom.dll:100AA4AC  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
100AB489  C:\Program Files\CodeBlocks\wxmsw26u_gcc_custom.dll:100AB489  _ZN12wxEvtHandler12ProcessEventER7wxEvent
100AB2C6  C:\Program Files\CodeBlocks\wxmsw26u_gcc_custom.dll:100AB2C6  _ZN12wxEvtHandler20ProcessPendingEventsEv
10001C94  C:\Program Files\CodeBlocks\wxmsw26u_gcc_custom.dll:10001C94  _ZN12wxAppConsole20ProcessPendingEventsEv
61850270  C:\Program Files\CodeBlocks\codeblocks.dll:61850270  Manager::ProcessPendingEvents()  D:/Devel/codeblocks/src/sdk/manager.cpp:90
6185577A  C:\Program Files\CodeBlocks\codeblocks.dll:6185577A  MessageManager::Log(int, wchar_t const*, ...)  D:/Devel/codeblocks/src/sdk/messagemanager.cpp:257
68F4E850  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F4E850  DebuggerGDB::DebugLog(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:436
68F675AB  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F675AB  GDB_driver::ParseOutput(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/gdb_driver.cpp:213
68F544FB  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F544FB  DebuggerGDB::ParseOutput(wxString const&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:1174
68F56177  C:\Program Files\CodeBlocks\share\codeblocks\plugins\debuggergdb.dll:68F56177  DebuggerGDB::OnGDBError(wxCommandEvent&)  D:/Devel/codeblocks/src/plugins/debuggergdb/debuggergdb.cpp:1438

The bug starts when an event triggers DebuggerGDB::OnGDBError. From there it's all downhill.

Apparently OnGDBError gets called over and over! There must be a reason for this...
(Is the event skipped before logging, or something?)

Well, at least this looks clearer than with wxYield's :P

I think we need to refine the ProcessPendingEvents to limit them to the actual DebugLogs... Yiannis, I may try to fix this tonight, but that means waiting 8 hours until i get out of the office... can you do it? Inside MessageManager, try replacing Manager::ProcessPendingEvents with (insert log here)->GetTextCtrl (or whatever)->ProcessPendingEvents...

We may need to add some "GetControl()" properties to the log classes...
« Last Edit: January 17, 2006, 05:46:29 pm by rickg22 »

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: debugger crashes
« Reply #8 on: January 17, 2006, 08:22:41 pm »
Quote
I think we need to refine the ProcessPendingEvents to limit them to the actual DebugLogs... Yiannis, I may try to fix this tonight, but that means waiting 8 hours until i get out of the office... can you do it? Inside MessageManager, try replacing Manager::ProcessPendingEvents with (insert log here)->GetTextCtrl (or whatever)->ProcessPendingEvents...

We may need to add some "GetControl()" properties to the log classes...

I 'll fix this. There is an easier way than exposing the control...
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: debugger crashes
« Reply #9 on: January 17, 2006, 10:03:43 pm »
cool, thanks! :)