Comments on: 2. Writing a new gdb command

By: tom

tom — Wed, 15 May 2013 18:02:24 +0000

@Haitham – I’m not actually sure. I suggest filing a bug report.

By: Haitham Gad

Haitham Gad — Wed, 13 Mar 2013 02:41:52 +0000

I have a question regarding prefix commands. I know that the gdb “logging” command is a prefix command:

set logging file “/tmp/log”
set logging overwrite on

But at the same time, you can give it values independently like:

set logging on
set logging off

In python, if I need to get the value of a sub-parameter, I use:

gdb.parameter(“logging file”)
gdb.parameter(“logging overwrite”)

But how to get the value of the “logging” parameter itself? I tried:

gdb.parameter(“logging”)

but it didn’t work.

Thanks,
Haitham

By: GDB???? | ????

GDB???? | ???? — Sun, 01 Jul 2012 14:06:43 +0000

[...] Writing a new gdb command [...]

By: Robin

Robin — Tue, 06 Mar 2012 14:42:23 +0000

At least with GDB 7.2 I’ve discovered that the source command shown above does not work. Instead you need to use the .py file extension and emit the -p, i.e.

(gdb) source /tmp/example.py

I guess things have moved on since this tutorial was written, but I still found it very helpful.

By: tom

tom — Tue, 23 Nov 2010 18:20:01 +0000

@JK – I suggest the gdb documentation. Most of the gdb module is defined in C code.

By: JK

JK — Tue, 23 Nov 2010 13:11:27 +0000

I am trying to extend gdb by creating custom commands using python. Can you please tell me where I can find the gdb class definition. I could not find all the methods available in gdb class.

By: Eric Freitas

Eric Freitas — Fri, 16 Jul 2010 18:33:54 +0000

Thanks for getting this functionality into gdb. It works really great. You really need to make it easier to install/use though. I have been searching and downloading and building gdb and archer to no avail until I found a note for Chromium that explained how to get the python pretty printing to work when debugging Chromium. It was simple and to the point.

http://code.google.com/p/chromium/wiki/LinuxDebugging

I think the main issue here is that there is a lot that you take for granted that a Linux dev should just know before trying to delve into the deep innards of simply modifying the .gdbinit file. I think that having a short, simple example of how to get it working with gdb 7+ would be great. The website above did that. It may not be perfect, but it works.

Thanks

By: tom

tom — Sat, 29 Nov 2008 21:42:31 +0000

Daniel — I don’t recall seeing the patch, though I could have missed it, particularly if it was sent before June or so.

It definitely is not in the tree:

(gdb) define delete foo
Junk in argument list: ” foo”

By: Daniel Jacobowitz

Daniel Jacobowitz — Sat, 29 Nov 2008 19:39:14 +0000

Mostly unrelated, but have we not posted the patch to add subcommands using define? If so, it’s not on purpose. It’s a handy and quite simple patch.

That doesn’t make this any less useful, mind!