Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
cbexaminr:
Can you explain the steps needed to reproduce the bug you try to fix with the attachpause.2.patch ?
The disassembly patch seems to cause the output command for the tooltip to be executed 3 time, can you investigate that?
p.s. I'm running gentoo linux amd64, if this can make a difference
p.p.s. The DebugBreakProcess is available in win2000+, so the debugger can't work in win98/ME
cbexaminr:
--- Quote from: oBFusCATed on October 23, 2010, 06:45:15 pm ---cbexaminr:
Can you explain the steps needed to reproduce the bug you try to fix with the attachpause.2.patch ?
--- End quote ---
On windows, Start c::b, attach to a process that you do not have a project open for, but which has been previously started outside of c::b. An initial break will occur (on windows at least) as a result of the initial attachment. Continue the target process from c::b. Then attempt to 'pause' the running process (I was using the toolbar icon, don't think I tried the menu option.)
(Codewise, the process is not paused, because m_Pid is not populated for an attached process, and a child is not found to attempt the 'break' on.)
I'm assuming similar circumstances would occur on Linux as well, assuming m_Pid and m_AttachToPid are handled the same as windows, but I didn't actually explore this outside of DoBreak().
--- Quote from: oBFusCATed on October 23, 2010, 06:45:15 pm ---The disassembly patch seems to cause the output command for the tooltip to be executed 3 time, can you investigate that?
--- End quote ---
OK, I'll see what happens to me on windows.
--- Quote from: oBFusCATed on October 23, 2010, 06:45:15 pm ---p.s. I'm running gentoo linux amd64, if this can make a difference
--- End quote ---
Don't know, could be some difference.
oBFusCATed:
Hm, works on linux, should do some testing on windows....
BTW, m_Pid is the PID of the debugger
p.s. the GdbCmd_StepOrNextInstruction and similar classes in the Disasm patch seems to be unused, can I remove them?
cbexaminr:
--- Quote from: cbexaminr on October 23, 2010, 08:03:38 pm ---
--- Quote from: oBFusCATed on October 23, 2010, 06:45:15 pm ---The disassembly patch seems to cause the output command for the tooltip to be executed 3 time, can you investigate that?
--- End quote ---
OK, I'll see what happens to me on windows.
--- End quote ---
Get three commands, but not repeats.
For a boolean variable bFirstTime, the three slightly different commands executed were:
whatis bFirstTime
output &bFirstTime
output bFirstTime
were all executed obtaining 1)type information, 2)address, and 3)variable contents.
Could that be what you are seeing? The disassembly patch has nothing to do with that, though.
cbexaminr:
--- Quote from: oBFusCATed on October 23, 2010, 08:20:36 pm ---p.s. the GdbCmd_StepOrNextInstruction and similar classes in the Disasm patch seems to be unused, can I remove them?
--- End quote ---
No. I'm pretty sure you'll find they are used if you remove them and try compiling. That one is a base for the other two commands. At the moment they're similar, but I chose to give each action its own command class in case they should need to diverge.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version