From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: Re: [MI] -file-list-exec-source-files
Date: Tue, 24 Feb 2004 04:26:00 -0000 [thread overview]
Message-ID: <20040224042635.GA17603@white> (raw)
In-Reply-To: <20040223135527.GA28267@nevyn.them.org>
On Mon, Feb 23, 2004 at 08:55:27AM -0500, Daniel Jacobowitz wrote:
> On Mon, Feb 23, 2004 at 08:13:35AM -0500, Bob Rossi wrote:
> > On Tue, Feb 17, 2004 at 02:33:27PM -0500, Daniel Jacobowitz wrote:
> > > On Tue, Feb 17, 2004 at 02:30:01PM -0500, Bob Rossi wrote:
> > > > On Tue, Feb 17, 2004 at 02:12:38PM -0500, Daniel Jacobowitz wrote:
> > > > > On Tue, Feb 17, 2004 at 02:10:05PM -0500, Bob Rossi wrote:
> > > > > > I have one last question that didn't get answered, could the psymtab be
> > > > > > modified to contain the dirname?
> > > > >
> > > > > Probably, but the dirname -> fullname conversion may be expensive - it
> > > > > involves a lot of stat() calls.
> > > >
> > > > I could definatly use some advice getting the dirname into the psymtab.
> > > > I don't mind spending time implementing it if I could get a little
> > > > pointer in the right direction. It seems I would have to change both the
> > > > stabs reader and the dwarf2 reader. Is that correct?
> > >
> > > Yes, I think so. Dwarf2 should be easy. Stabs will be a little
> > > harder. Take a look at patch_subfile_names.
> >
> > Thanks, I think I got the Stabs version working.
> > Do you have a heads up for the Dwarf2 version?
> >
> > Funny enough, Stabs was much easier for me to get done than Dwarf2.
> > I am currently looking at the function dwarf2_build_psymtabs_hard.
> > Does this sound right?
> >
> > As far as I know, this will be the last step to the patch I'm
> > generating. Also, I will only have Stabs and Dwarf-2 working. Anyone
> > know of another debug format I should be looking into?
> >
> > Any help would be appreciated,
>
> I'd think dwarf2 would be downright easy in comparison. All you want
> is the comp_unit_die in dwarf2_build_psymtabs_hard. read_partial_die
> does not currently save DW_AT_comp_dir, the compilation directory, but
> making it do so would be easy.
Thanks, with your help, this turned into a 5 minute problem!
I'll be posting the patch soon, just have to clean up the code now.
Thanks a lot!
Bob Rossi
next prev parent reply other threads:[~2004-02-24 4:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 1:29 Bob Rossi
2004-02-16 1:26 ` Bob Rossi
2004-02-16 1:42 ` Kip Macy
2004-02-16 3:19 ` Bob Rossi
2004-02-16 3:30 ` Daniel Jacobowitz
2004-02-16 3:45 ` Bob Rossi
2004-02-16 3:49 ` Daniel Jacobowitz
2004-02-16 15:33 ` Bob Rossi
2004-02-16 15:46 ` Daniel Jacobowitz
2004-02-16 16:08 ` Bob Rossi
2004-02-17 18:22 ` Andrew Cagney
2004-02-17 19:10 ` Bob Rossi
2004-02-17 19:12 ` Daniel Jacobowitz
2004-02-17 19:30 ` Bob Rossi
2004-02-17 19:33 ` Daniel Jacobowitz
2004-02-23 13:13 ` Bob Rossi
2004-02-23 13:55 ` Daniel Jacobowitz
2004-02-24 4:26 ` Bob Rossi [this message]
2004-02-27 6:23 ` Bob Rossi
2004-02-27 15:00 ` Daniel Jacobowitz
2004-02-17 19:47 ` Andrew Cagney
2004-02-17 20:02 ` Bob Rossi
2004-02-17 20:27 ` Andrew Cagney
2004-02-17 21:08 ` Bob Rossi
2004-02-17 21:37 ` Daniel Jacobowitz
2004-02-17 21:58 ` Bob Rossi
2004-02-18 14:24 ` Alain Magloire
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=20040224042635.GA17603@white \
--to=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