Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Frame issue with the debugger plugin

<< < (5/14) > >>

scarphin:

--- Quote from: oBFusCATed on April 08, 2015, 01:12:51 am ---Hm, you've added a single breakpoint and the debugger stops at it.
Why are you saying that it fails to do so?

--- End quote ---
Because it's the breakpoint:

--- Code: ---[debug]> break "D:/coding/projects/sw/codeblocks/trunk/src/plugins/debuggergdb/gdb_commands.h:1207"
[debug]Breakpoint 3 at 0x6daaa2d1: file D:/coding/projects/sw/codeblocks/trunk/src/plugins/debuggergdb/gdb_commands.h, line 1207.
--- End code ---
at line 142 of the debug log that it doesn't stop.

oBFusCATed:
It has stopped on the breakpoint and then you've hit the continue button. According to the log.
Have you hit the continue button?

scarphin:
No, unfortunately.

scarphin:
There are 2 bugs regarding the original problem.
1- The reason for the invalid frame numbers are the 'ToULongLong' conversions in 'GdbCmd_Backtrace::MatchLine' function in 'gdb_commands.h'. There is a bug report here:
http://trac.wxwidgets.org/ticket/13282
2- 'm_number' is defined as 'int' in the 'cbStackFrame' class but it is converted to and from a 'size_t' type in the previously mentioned function. It should be defined as 'ssize_t' if it's required to be a signed type, 'size_t' otherwise. Also 'validFrameNumber' variable in function 'GdbCmd_Backtrace::ParseOutput' should match 'm_number's type.

oBFusCATed:
Thanks for the digging this up. I'll see what can be done to fix it.

Can you try to build the test project (see in the debuggergdb folder)?

Navigation

[0] Message Index

[#] Next page

[*] Previous page