Comments on: 9. Scripting gdb

By: tom

tom — Wed, 15 May 2013 18:03:31 +0000

@Michael – there may not be a way right now. I think symbol table iteration is not very well supported yet. Please file a bug.

By: Michael K

Michael K — Wed, 24 Apr 2013 06:40:32 +0000

Hello Tom,

first of all thank you for your great work, python scripting is a great feature in GDB!

I have a question which I would like to ask you at this place: How can I get an iterator over the global symbol table without having a valid stack frame? I want to write a script which prints out some information on global symbols from within .gdbinit, before execution has been started. I am using GDB 7.5.

Any hint on this would be greatly appreciated!

Michael.

By: Scripting GDB Links « Constantly Underwhelmed

Scripting GDB Links « Constantly Underwhelmed — Fri, 09 Mar 2012 07:07:26 +0000

[...] http://tromey.com/blog/?p=548 [...]

By: The Cliffs of Inanity › 12. Events

The Cliffs of Inanity › 12. Events — Fri, 06 Jan 2012 15:05:04 +0000

[...] wrote a little about events in gdb-python post #9 — but a lot has changed since then. A Google SoC student, Oguz Kayral, wrote better support [...]

By: Sam

Sam — Mon, 09 Nov 2009 06:02:50 +0000

Unless I am mistaken it seems that support for controlling processes and catching events has not yet been merged.

The closest I can find is the patches submitted by Oguz Kayral in August http://sourceware.org/ml/archer/2009-q3/msg00148.html which do not seem to be merged into git yet. I will be looking forward to this getting added.

By: erik

erik — Mon, 27 Jul 2009 08:29:53 +0000

I was trying out the python support in gdb today. Great work so far! At last we will be able to do the custom debugger for our platform that we have wanted for a while. “GDB as a module” makes a lot of sense.

I tried running our old python hack that communicates with gdb through a subprocess through gdb -P just to see what would happen and it immediatly stumbled upon the fact that argv[0] is not set to the script name. This makes it incompatible with some pretty useful modules like the OptionParser.

And by the way, if there is a better way to report a bug, please let me know!

As I said, great work so far!

By: tom

tom — Fri, 13 Feb 2009 16:09:08 +0000

Right, you have to use git and you must check out the correct branch.
See the archer pages on the gdb wiki for more information on how to do that.

By: yzc

yzc — Fri, 13 Feb 2009 00:51:15 +0000

I first tried to use the git client, but it didn’t
work when I tried “git clone git://sourceware.org/git/archer.git”
or “git clone ssh://sourceware.org/git/archer.git”.
Then I went to http://sourceware.org/git/gitweb.cgi?p=archer.git,
picked http://sourceware.org/git/gitweb.cgi?p=archer.git;a=snapshot;h=ad88187efac2686ec0b15c558e05262a003ba504;sf=tbz2

So, guess the one with python support can only be
obtained with git?

By: tom

tom — Fri, 13 Feb 2009 00:21:59 +0000

yzc – I don’t think we’ve made an “archer gdb tarball”.
Where did you get it?

Also, for best results, send email to the archer list.
You don’t have to be a member.

By: yzc

yzc — Thu, 12 Feb 2009 22:48:06 +0000

Very interesting! I tried to build the archer gdb tarball
with “./configure –with-python”; but the produced gdb
doesn’t recognize “-P” or “–python” option. What might be
missing? Thanks, -Yan

—————————————————–
$ ./gdb -P
./gdb: unrecognized option `-P’
Use `./gdb –help’ for a complete list of options.
$ ./gdb –python [1]
./gdb: unrecognized option `–python’
Use `./gdb –help’ for a complete list of options.