Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
cbexaminr:
Next disasm .5h. changes iteration (comment changes and variable name change, should be no other code changes from oBFusCATed last mods [.5g. skipped])
Possible submit notes:
1)Check UpdateDisassembly() rather than UpdateBacktrace() for CMD_STEP_INTO_INSTR handling
2)Call NotifyCursorChanged() on CMD_STEP_INTO_INSTR and CMD_STEP_INSTR to update any of various affected windows that may be open
3)Modify disassembly display functionality in effort to
a)reduce number of times (re-)disassembly requested from gdb
b)when possible avoid total redraw of disassembly and
simply reposition "current" instruction gutter indicator
c)correct (one) possible disassembly display failure when program position
moved to lower memory address
4)Modify some of stack frame change response handling to avoid disassembly of area on
autoswitch since may not reflect current program instruction
5)Support "Mixed Mode" disassembly display
6)Add functionality to let user quickly switch "current" instruction position between top/middle/bottom of disassembly window
7)Correct cut-n-paste comment error on GdbCmd_InfoRegisters
*NOTES (with regard to mingw-built GDB 7.2):
A)Response information returned from GDB is sometimes missing current instruction address which results in some (re-)disassembly that might otherwise be avoided. (I have not found an architecture independent means of determining the current instruction address to work-around these omissions. GDB's "$pc" changes according to the currently selected stack frame, which may be changed by autoswitch functionality, so cannot be used.)
B)Response information returned from GDB for a mixed mode disassembly sometimes fails to include instructions that are present in the target. Hence they cannot be found and indicated in the disassembly display.
MortenMacFly:
--- Quote from: cbexaminr on November 13, 2010, 05:21:17 pm ---Next disasm .5h. changes iteration (comment changes and variable name change, should be no other code changes from oBFusCATed last mods [.5g. skipped])
--- End quote ---
@oBFusCATed: Do you believe we should apply this now by in the branch and test it through a nightly build?
oBFusCATed:
I will look at it tonight...
cbexaminr:
oBFusCATed,
There was also the attach/pause patch, "attachpause.2.patch" (attached in post http://forums.codeblocks.org/index.php/topic,10908.msg91188.html#msg91188)
One of your posts (http://forums.codeblocks.org/index.php/topic,10908.msg91225.html#msg91225) seemed to suggest you had both observed the issue and seen that the patch corrected the problem (but I wasn't certain that's what you were referring to with the "Hm, works on linux" comment).
Is there currently any reason not to apply the "attachpause.2.patch" (from post http://forums.codeblocks.org/index.php/topic,10908.msg91188.html#msg91188)?
oBFusCATed:
--- Quote from: cbexaminr on November 17, 2010, 10:56:59 am ---... (but I wasn't certain that's what you were referring to with the "Hm, works on linux" comment)....
--- End quote ---
It means that it works without the patch.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version