Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: [MI] -file-list-exec-source-files
Date: Tue, 17 Feb 2004 19:33:00 -0000	[thread overview]
Message-ID: <20040217193327.GA31855@nevyn.them.org> (raw)
In-Reply-To: <20040217193001.GB5982@white>

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.

> I don't think the dirname->fullname conversion is bad at all. Well, at
> least relative to looking up the fullname without the dirname.
> 
> Either, you lookup the fullname without the dirname, by using openp,
> which has say N lookup attempts ( N-1 dir search path entries + 1
> entry for the cwd ) 
>    or
> you lookup the fullname with dirname, by using open_source_file, which
> add's 1 to that value of N ( by putting dirname in front ), and then
> calls openp.
> 
> So, I think looking up the fullname with or without knowing the dirname
> yeilds the same magnitude of work. However, if openp is implemented poorly, 
> I could also look into that.

My point was not that one of these would be pricier than the other, but
that they are both pricy.  For a large application, doing this
conversion for all files will substantially penalize your startup time. 
Not to mention having to redo most of it when a new dir is added...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-17 19:33 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 [this message]
2004-02-23 13:13                       ` Bob Rossi
2004-02-23 13:55                         ` Daniel Jacobowitz
2004-02-24  4:26                           ` Bob Rossi
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=20040217193327.GA31855@nevyn.them.org \
    --to=drow@false.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