From: "Eli Zaretskii" <eliz@elta.co.il>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: Executable's debug format
Date: Fri, 13 Feb 2004 09:11:00 -0000 [thread overview]
Message-ID: <9003-Fri13Feb2004111212+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040213005432.GA4476@white> (message from Bob Rossi on Thu, 12 Feb 2004 19:54:32 -0500)
> Date: Thu, 12 Feb 2004 19:54:32 -0500
> From: Bob Rossi <bob@brasko.net>
>
> Is there a way to find out what debug format the debugging info in the
> executable is in?
>
> Or is it more complicated? Can a single executable be composed of object
> files which each have there debugging info in a different format?
Yes, it can.
The command "info source" will show you the debug info with which the
current source file (the one where the program counter is now) was
compiled. For example, to see the debug info format for the source
file where your `main' function lives, type these commands:
(gdb) break main
(gdb) run
(gdb) info source
next prev parent reply other threads:[~2004-02-13 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 0:54 Bob Rossi
2004-02-13 3:03 ` Ian Lance Taylor
2004-02-16 3:32 ` Daniel Jacobowitz
2004-02-13 9:11 ` Eli Zaretskii [this message]
2004-02-13 14:48 ` Kris Warkentin
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=9003-Fri13Feb2004111212+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=bob@brasko.net \
--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