Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefano.sabatini-lala@poste.it>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: How to show the file being executed?
Date: Sat, 20 Feb 2010 14:06:00 -0000	[thread overview]
Message-ID: <20100220140504.GA11702@geppetto> (raw)
In-Reply-To: <E1NioaI-0006be-0D@fencepost.gnu.org>

On Saturday 2010-02-20 07:37:22 -0500, Alfred M. Szmidt wrote:
>    (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.
> 
> You can use readelf to get most of that information.

I want to show *only* the local exec file as specified by the "file"
command, and within a gdb script, currently the only way I see is to
use info target.

Regards.


  reply	other threads:[~2010-02-20 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 12:26 Stefano Sabatini
2010-02-20 12:37 ` Alfred M. Szmidt
2010-02-20 14:06   ` Stefano Sabatini [this message]
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=20100220140504.GA11702@geppetto \
    --to=stefano.sabatini-lala@poste.it \
    --cc=ams@gnu.org \
    --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