Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Splitting debugger in two - specific debugger and common GUI

<< < (31/136) > >>

oBFusCATed:
Done... and here is the next patch:

http://smrt.is-a-geek.org/codeblocks/dbg_refactor0008.patch

What is done:
1. Moved more methods to the base class - related to the project compilation and running the console on *nix
2. From now on there will be only one debugger toolbar.
3. Split Break and Stop buttons on the toolbar - need an icon for the break button
4. Watch improvements:
4.1. Added a Type column.
4.2. Now the user add watches by dragging string onto the watch window
5. Ensure the active thread is visible in the thread dialog
6. When the last debugger plugin is unloaded close all the debugger windows
7. Reimplemented the feature that allows the user to add breakpoints while the debuggee is running
8. Remember the last active debugger

I've introduce some bug related to the attaching to processes, which I've marked with FIXMEs and I hope I'll fix them soon.

PLEASE TEST, because I'm sure no one is running the debugger branch actively (or is shy to report problems). The branch before this was crashing annoyingly and badly when adding and removing breakpoints while the debuggee was running.

Also any feedback on the gdb/mi plugin is quite welcome.

Best regards....

MortenMacFly:

--- Quote from: oBFusCATed on January 04, 2010, 11:43:47 pm ---http://smrt.is-a-geek.org/codeblocks/dbg_refactor0008.patch

--- End quote ---
Hey - we were already there, see here:
http://forums.codeblocks.org/index.php/topic,10908.msg79425.html#msg79425

I'll rename it to 0009... ;-)

MortenMacFly:

--- Quote from: oBFusCATed on January 04, 2010, 11:43:47 pm ---The branch before this was crashing annoyingly and badly when adding and removing breakpoints while the debuggee was running.

--- End quote ---
I knew but as it was easy to fix I though you had handled that already...

MortenMacFly:

--- Quote from: oBFusCATed on January 04, 2010, 11:43:47 pm ---http://smrt.is-a-geek.org/codeblocks/dbg_refactor0008.patch

--- End quote ---
Hmmm... with this patch applied I cannot debug C::B anymore.
I am placing a BP in "MainFrame* CodeBlocksApp::InitFrame()" (src/app.cpp) and hit "debug".
this is what I see in the debug log:
> break "C:/Devel/CodeBlocks/src/src/app.cpp:401"
Breakpoint 1 at 0x4026ab: file C:\Devel\CodeBlocks\src\src\app.cpp, line 401.
>>>>>>cb_gdb:
> run
pid=3060 tid=5908 code=LOAD_DLL_DEBUG_EVENT)
gdb: Loading dll "C:\WINDOWS\system32\ws2help.dll" at 0x71a00000.
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
gdb: kernel event for pid=3060 tid=5908 code=LOAD_DLL_DEBUG_EVENT)
gdb: Loading dll "C:\Devel\CodeBlocks\src\devel\codeblocks.dll" at 0xb10000.
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
gdb: kernel event for pid=3060 tid=5908 code=LOAD_DLL_DEBUG_EVENT)
gdb: Loading dll "C:\Devel\CodeBlocks\src\devel\wxpropgrid.dll" at 0x6e440000.
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
gdb: kernel event for pid=3060 tid=5908 code=LOAD_DLL_DEBUG_EVENT)
gdb: Loading dll "C:\Devel\CodeBlocks\src\devel\wxscintilla.dll" at 0x6c980000.
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
gdb: kernel event for pid=3060 tid=5908 code=EXCEPTION_DEBUG_EVENT)

Then nothing happens and I can only stop the debugger (only "break" and "stop" is available, but "break" does nothing).

when I hit "stop" this is in the debug log:
Exception condition detected on fd 0
error detected on stdin
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
ContinueDebugEvent (cpid=3060, ctid=4612, DBG_CONTINUE);
ContinueDebugEvent (cpid=3060, ctid=5908, DBG_CONTINUE);
ContinueDebugEvent (cpid=3060, ctid=4612, DBG_CONTINUE);
gdb: windows_close, inferior_ptid=3060

Any hints???

MortenMacFly:
Nargh... just forget about this. I still had the patch of yours applied concerning PipedProcess. This has bitten me literally the first time now. I've removed this for now and forever and suddenly all works again (including debugging wx apps). It shows that this patch is not working reliable and we'd better not apply it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version