From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: gdb Mailing List <gdb@sources.redhat.com>
Subject: How to show the file being executed?
Date: Sat, 20 Feb 2010 12:26:00 -0000 [thread overview]
Message-ID: <20100220122449.GA9150@geppetto> (raw)
Hi all,
I'm running gdb 7.0 and first of all let me thank you, it's simply
*AWESOME*, reversible debugging and scripting are some features we
always dreamt for, and now they're finally available to all the free
world, thanks!!
I have a small problem, I need to show the name of the file debugged
in a gdb script, and info target looks overkill as it shows too much
information.
(gdb) show version
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) info target
Symbols from "/home/stefano/src/PROGRAM".
Unix child process:
Using the running image of child Thread 0xb5f33b70 (LWP 8998).
While running this, GDB does not access memory from...
Local exec file:
`/home/stefano/src/PROGRAM', file type elf32-i386.
Entry point: 0x804bc70
0x08048134 - 0x08048147 is .interp
0x08048148 - 0x08048168 is .note.ABI-tag
0x08048168 - 0x0804818c is .note.gnu.build-id
[...]
There is some way to show *only* this information?, otherwise I suggest
to implement a show file command.
Regards.
next reply other threads:[~2010-02-20 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 12:26 Stefano Sabatini [this message]
2010-02-20 12:37 ` Alfred M. Szmidt
2010-02-20 14:06 ` Stefano Sabatini
2010-02-23 19:25 ` Alfred M. Szmidt
2010-02-23 19:35 ` Pedro Alves
2010-02-23 20:51 ` Pedro Alves
2010-02-24 16:54 ` Alfred M. Szmidt
2010-02-24 16:46 ` Alfred M. Szmidt
2010-02-24 17:01 ` Pedro Alves
2010-02-24 17:26 ` Pedro Alves
2010-02-25 15:28 ` Alfred M. Szmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100220122449.GA9150@geppetto \
--to=stefano.sabatini-lala@poste.it \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox