User forums > Nightly builds
The 11 March 2007 build is out.
TDragon:
--- Quote from: nenin on March 12, 2007, 03:38:48 pm ---If gdb does not use this missed call, it is not necessary.
--- End quote ---
GDB doesn't in and of itself support pausing a running process without a breakpoint already being set.
If you look in Code::Blocks' debuggergdb.cpp, you'll find the function Stop(), which basically "injects" a breakpoint into the child process being debugged. In Unix-style systems, for which GDB was designed, this is quite simple: send a SIGINT (interrupt signal) to the process. In Windows, to get a proper debuggable break, a breakpoint exception (of the Win32 structured exception handling variety, not the C++ variety) has to be raised. DebugBreakProcess, which is only available since XP, basically does this by creating a new thread remotely in the debuggee process, with an entry point at DbgUiRemoteBreakin in ntdll, which then raises the breakpoint exception.
nenin:
--- Quote from: Pecan on March 12, 2007, 03:45:02 pm ---<***>
The DebugBreakProcess() and DebugBreak() calls in XP allow breaking a run away program, infinite looping, etc, just like Ctrl-C works in Unix.
CB added it to the debugger Stop button to allow a user to debug a loop,a runaway, or break at will to see a backtrace, variables, etc.
Evidently, it only comes with the XP kernel.
--- End quote ---
OK. It is very nice, but I guess it may be implemented separately for WinXP and higher and just disabled for Win2K and bellow.
Pecan:
--- Quote from: nenin on March 12, 2007, 03:55:29 pm ---
--- Quote from: Pecan on March 12, 2007, 03:45:02 pm ---<***>
The DebugBreakProcess() and DebugBreak() calls in XP allow breaking a run away program, infinite looping, etc, just like Ctrl-C works in Unix.
CB added it to the debugger Stop button to allow a user to debug a loop,a runaway, or break at will to see a backtrace, variables, etc.
Evidently, it only comes with the XP kernel.
--- End quote ---
OK. It is very nice, but I guess it may be implemented separately for WinXP and higher and just disabled for Win2K and bellow.
--- End quote ---
I'm sure mandrav or another core developer will fix this as soon as they can.
nenin:
--- Quote from: Pecan on March 12, 2007, 04:09:20 pm ---I'm sure mandrav or another core developer will fix this as soon as they can.
--- End quote ---
Saying frankly it is a first and single reason for me to try WinXP on my workplace.
orefa:
I also lack any reason to leave good old faithful Win2K, except that I also had to revert to CB_20070308. I have XP on a laptop since it was preloaded. Other than that, following any hardware upgrade, 2K goes right back on my desktop. No activation required either (thanks a lot Vista!) and everything just works.
Now of course, if software support disappears for it then I will have little choice. I won't even have a choice to upgrade to XP since MS is taking it off the shelves. So it will have to be either Vista, uugh, or a move to Mac or Linux. I hope CB will continue to support 2K for as long as possible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version