From: Eli Zaretskii <eliz@elta.co.il>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: -file-list-exec-source-files implementation
Date: Tue, 16 Dec 2003 06:06:00 -0000 [thread overview]
Message-ID: <ur7z52t2j.fsf@elta.co.il> (raw)
In-Reply-To: <20031216001040.GA7871@white> (message from Bob Rossi on Mon, 15 Dec 2003 19:10:40 -0500)
> Date: Mon, 15 Dec 2003 19:10:40 -0500
> From: Bob Rossi <bob@brasko.net>
>
> I prefer the first alternative if it is possible to look up the fullpath
> to all of the file's that the exe is made up of.
Isn't it possible that the sources are actually in a different
directory than the one recorded in the debug info, and if so, isn't it
true that GDB allows to work with sources in such a case by means of
the appropriate `dir' command?
In such a case, the first alternative is not the way to go, as it will
return unusable file names, and the way CLI does it is better, I
think.
next prev parent reply other threads:[~2003-12-16 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 0:10 Bob Rossi
2003-12-16 6:06 ` Eli Zaretskii [this message]
2003-12-31 19:34 ` Andrew Cagney
2004-02-07 2:23 ` Bob Rossi
2004-02-07 2:27 ` Kip Macy
2004-02-07 14:41 ` Bob Rossi
2004-02-07 19:02 ` Kip Macy
2004-02-10 21:59 ` Andrew Cagney
2004-02-10 22:02 ` Bob Rossi
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=ur7z52t2j.fsf@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