Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Suggest on the debugger plugin
ollydbg:
Hi, it seems there is a "=>" arrow in the debugger log. but this is not shown in the Disassemble window. See the image below:
oBFusCATed:
Ollydbg: You'll have to debug this issue yourself. Please set breakpoints at the callers of SetActiveAddress() and investigate what is going wrong.
On my machine it works, unfortunately, and I can't test it on windows at the moment.
p.s. the => is not parsed and used...
p.p.s. tested on debuggers branch and with trunk on linux 64bit
p.p.p.s. you could test it with older gdb's 6.8 for example.
ollydbg:
--- Quote from: oBFusCATed on July 09, 2010, 11:33:38 pm ---Ollydbg: You'll have to debug this issue yourself. Please set breakpoints at the callers of SetActiveAddress() and investigate what is going wrong.
On my machine it works, unfortunately, and I can't test it on windows at the moment.
p.s. the => is not parsed and used...
p.p.s. tested on debuggers branch and with trunk on linux 64bit
p.p.p.s. you could test it with older gdb's 6.8 for example.
--- End quote ---
I just set a breakpoint in the first line of SetActiveAddress function, and found that this breakpoint never be hit. not sure what's the problem is. (I'm use the latest mingw cvs gdb 20100708, Loaden MinGW GCC 4.4.4, ccbranch).
By the way, it is quite cool to debug cb in cb.
That is CB->gdb->CB->gdb->test hello world app. (The arrow " ->" means function call) :D
oBFusCATed:
--- Quote from: ollydbg on July 10, 2010, 12:57:00 pm ---I just set a breakpoint in the first line of SetActiveAddress function, and found that this breakpoint never be hit
--- End quote ---
It is obvious that the breakpoint won't be hit. Set breakpoints around lines which call the SetActiveAddress() function. Most probably the regexes don't match as Jens suggested.
Have you tested the old gdbs?
ollydbg:
--- Quote from: oBFusCATed on July 10, 2010, 10:58:05 pm ---Have you tested the old gdbs?
--- End quote ---
Ok, I have download an old gdb, which is: Release Candidate_ GDB 6.8-3, but it is the same result as the new gdb 7.2.50 cvs.
There is no "EIP instruction arrow" appeared in the Disassembly windows either.
--- Quote ---It is obvious that the breakpoint won't be hit. Set breakpoints around lines which call the SetActiveAddress() function. Most probably the regexes don't match as Jens suggested.
--- End quote ---
I will do more test if I have time. Thanks for the help.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version