User forums > Nightly builds
The 27 November 2010 build (6863) DEBUGGER BRANCH version is out.
mushakk:
Thanks and good job!
:D
oBFusCATed:
killerbot: can you paste the debugger's debug log? :lol: 8)
killerbot:
voila, on my linux box I switched to the debugger branch :-)
Some first requests/issues.
In a program I want to be able to use CTRL-Z. However the debugger (gdb) is going to catch this, so where I normally would issue the following command in gdb :
--- Code: ---handle SIGTSTP nostop noprint pass
--- End code ---
I know added this to the Debugger settings -> Debugger intialization commands [note the typo in CB : intialization] :
--- Code: ---handle SIGTSTP nostop noprint pass
--- End code ---
When the debugger session from within CB has started, I check the Debugger->Information->Signal handling, and we see a nice entry : no no yes.
So this is good, however inside the program, cntrl-Z does NOT do what it supposed to do.
This does however work when the program was launched through gdb on the command line (and issueing the handle command in gdb).
Any idea why this doesn't work when the launch happened from CB ?
Request : currently we show the signal table purely informational, wouldn't it be nice that this table could be modified, so we can hide the handle command alltogether, and maybe CB could store this information so it doesn't have to be entered each time ?
What do you guys think ?
killerbot:
Another request :
During a debugging session, one ends up at a given statement in a certain file.
Then one browse around :
- opening other files to look up something
- selecting another frame from the call stack
- ...
Result : you get lost ;-) and have no clue where your last executed statement was, and you want to return to that statement, so you can "see your" "next line" action.
Currently this can be done by going to the callstack and click on the deepest level.
It would be nice, if there was a dedicated button for that in the toolbar, I have seen it in other IDE's (typically the yellow arrow), which just brings the editor of the file containing the "next to execute" statement.
What do you think ?
oBFusCATed:
--- Quote from: killerbot on November 30, 2010, 11:43:27 am ---In a program I want to be able to use CTRL-Z. However the debugger (gdb) is going to catch this, so where I normally would issue the following command in gdb :
....
When the debugger session from within CB has started, I check the Debugger->Information->Signal handling, and we see a nice entry : no no yes.
So this is good, however inside the program, cntrl-Z does NOT do what it supposed to do.
This does however work when the program was launched through gdb on the command line (and issueing the handle command in gdb).
Any idea why this doesn't work when the launch happened from CB ?
--- End quote ---
Have you tried this:
1. start gdb
2. start terminal
3. attach the output of the inferior/debuggee to the terminal using the tty command
4. same as before
My guess is that ctrl+Z is handled inside gdb, not in the debuggee, so if you execute ctrl+z in the terminal there is no way for gdb to receive the signal.
--- Quote from: killerbot on November 30, 2010, 11:50:05 am ---It would be nice, if there was a dedicated button for that in the toolbar, I have seen it in other IDE's (typically the yellow arrow), which just brings the editor of the file containing the "next to execute" statement.
What do you think ?
--- End quote ---
It is easy to do, but I'm not sure if it is good to waste more space in the toolbar...
Most of the time the Callstack window is too usefull to be closed/hidden:)
But I've added it to my todo, some day I could implement it...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version