Issue with step-wise debugging (F7) in debugger branch

[MortenMacFly]

I experience an issue with the current SVN head version of the debugger branch:

Stepwise debugging ("next line", F7) seems not to work for me anymore or at least works not reliable. Whenever I hit "F7" is sometimes steps to the next line in the code, but then suddenly somewhere completely different - sometimes it steps deeper into the code, sometimes it seems to step out.

Does anyone else experience the same??? I'll try to create a debug-log, but often in addition the IDE freezes and never returns. I cannot even kill the child nor the debugger in that case, I have to kill the C::B instance running the debugger.

OS: WinXP-SP3, Compiler: TDM 4.5.2, Debugger: "GNU gdb (GDB) 7.2" (also from TDM webpage).

[oBFusCATed]

Can you try a debug version of C::B and when it locks to attach a gdb to it and see where it has locked itself?

I have  (almost) no locks or crashes related to the debugger, only CC crashes...

This is on Linux, on windows7 is very bad story, but I'm not sure what it is causing it.

[MortenMacFly]

Can you try a debug version of C::B and when it locks to attach a gdb to it and see where it has locked itself?

How? Using another C::B instance?

[oBFusCATed]

Yes or using gdb directly from the command line.

[oBFusCATed]

Stepwise debugging ("next line", F7) seems not to work for me anymore or at least works not reliable. Whenever I hit "F7" is sometimes steps to the next line in the code, but then suddenly somewhere completely different - sometimes it steps deeper into the code, sometimes it seems to step out.

I've seen this on optimized code, but I think this is normal and this is GDB feature, than something broken in C::B

[MortenMacFly]

I've seen this on optimized code, [...]

The debug code is not optimised. I always have a special debug target with optimisations turned off and debug symbols turned on. So this most likely isn't the case here.

In the moment I am not debugging though... (my code is error free... for the moment... ;-)).

[oBFusCATed]

OK, next time you see it, please inspect the debug log, but I highly doubt there is something broken in this part of the debugger