User forums > Nightly builds

The 11 February 2012 build (7790) DEBUGGER BRANCH version is out.

<< < (9/11) > >>

ollydbg:

--- Quote from: ollydbg on February 24, 2012, 02:56:44 am ---
--- Quote from: p2rkw on February 24, 2012, 02:42:41 am ---ok, got it, printer works very well, but there is another problem:
After "python" command gdb doesn't recognize "end" command

--- End quote ---
I can confirm that enter some command like:

--- Code: ---python
print 3
end

--- End code ---
But it looks like the "end" command does not recognized by gdb. maybe, the "end" command does not send correctly to gdb. so I can't run any command after that.

I just tested gdb under command line, and it works fine, "end" command can successfully end the “python" session, so it looks like something should be fixed in debugger plugin's source.  :)

--- End quote ---

Ok, from the experience I debug the debugger branch source several days ago, I think the bug is that:
Our debugger plugin do a hand shake on every command you send to gdb, the mechanism is:
1, you send a command to gdb
2, gdb return the value, and restore the gdb's prompt

But in the case that we send command "python", gdb does not return a standard "gdb prompt", but it return a short ">" to wait the user to continuously enter other python commands until it receive "end", so this break the original handshake rule.  :)

oBFusCATed:
Just use source. I doubt, I'll fix anything here.

p2rkw:
Ok, I'll use source.

Why in debugger branch automatic locals and args watching is disabled? I have got both relevant options turned on in debugger settings panel, but plugin doesn't send messages(info locals, info args) when the program is paused. win xp 32.

oBFusCATed:
Because I've not implemented them back.

ollydbg:

--- Quote from: p2rkw on February 24, 2012, 05:49:57 pm ---Ok, I'll use source.

Why in debugger branch automatic locals and args watching is disabled? I have got both relevant options turned on in debugger settings panel, but plugin doesn't send messages(info locals, info args) when the program is paused. win xp 32.


--- End quote ---

Another reason is that "info locals" will cause the gdb(python enabled, at least under Windows) crash when it try to show an uninitialized local variables. You can search this forum or gdb maillists for some discussion.

Navigation

[0] Message Index

[#] Next page

[*] Previous page