User forums > General (but related to Code::Blocks)

Debuger - confusion (F7 does not work)

<< < (2/3) > >>

oBFusCATed:
From the log we can see that CB has issued next command and gdb jumped from line 155 to line 174.
From the explanation in the first post it is not clear what is the code at line 155 and line 174.

Can you clarify? Also can you run command line debugger and execute the same commands? I'm sure you'll get the same effect.

wever:
You can see it here:
http://paste.ideaslabs.com/show/Vr8qwnZY3s
The pasted code will be published 24h

I described where it jumps:

--- Code: ---I remove the line with printf("OH YES;"); ... so it jumps directly onto the line with blockDepthParser(w, &s, goOn); (there is breakpoint) ...
--- End code ---

So online 176, to test the behaviour, I make comment:
//printf("OH YES");
and then I run the debugger, I press F8 to the first breakpoint on line 155, then I press F7 and it suddenly jumps to line 174 ... blockDepthParser(w, &s, goOn);

oBFusCATed:
Can you execute a list gdb command after you've pressed f7 and debugger has stopped at the wrong place?
This command will print the code as gdb sees it.
It is possible that what gdb and what cb see as code and line number differs.

Also please try command line gdb and probably newer version of gdb (there are 4 versions after 7.5)

wever:
"execute a list gdb command"
How to do that? Do you mean "Send user command to debugger?" What commands?

oBFusCATed:
When cb has stopped on a breakpoint go to the debugger log tag, at the bottom there is a command field.
Enter 'list' (without quotes) and press enter.

Navigation

[0] Message Index

[#] Next page

[*] Previous page