Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	Eli Zaretskii <eliz@elta.co.il>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC/dwarf-2] Add support for included files
Date: Sat, 01 May 2004 04:57:00 -0000	[thread overview]
Message-ID: <vt24qr0lpei.fsf@zenia.home> (raw)
In-Reply-To: <20040501011418.GG16083@gnat.com>


Joel Brobecker <brobecker@gnat.com> writes:
> > - Is it really okay to pass NULL to dwarf_decode_lines for comp_dir?
> >   Won't the filenames of the partial symbol tables be different from
> >   those of the symbol tables?  To fix this, read_partial_die would
> >   have to check for DW_AT_comp_dir attributes, too.
> 
> I don't think we need to worry about the comp_dir when building
> the psymtabs for included files. The filename used for the psymtab
> is the same as the filename used to build the symtab (checked it
> by inspecting start_subfile() and end_symtab()). The only thing
> we could gain from computing the comp_dir as well during that phase
> is to compute the psymtab fullname. But then comp_dir is used
> to set the symtab dirname, not to compute the fullname. So it doesn't
> help improve the consistency between psymtab and symtab.

Let me make sure I've got it right.  When we're calling
dwarf_decode_lines for the partial symbol tables, we never call
dwarf2_start_subfile anyway --- that's for building full symbol tables
--- so the use of 'dirname' in that function doesn't matter.  And
since it's never used to compute the full name of the symtabs, it
doesn't introduce inconsistencies to omit it.

If that's correct, then this patch is ready to commit.  Thanks very
much!


  reply	other threads:[~2004-05-01  4:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 16:05 Jim Blandy
2004-04-13  5:20 ` Joel Brobecker
2004-04-14 19:10   ` Jim Blandy
2004-04-15 22:13     ` Joel Brobecker
2004-04-16  4:24       ` Jim Blandy
2004-04-16  4:28         ` Joel Brobecker
2004-04-16 23:08         ` Joel Brobecker
2004-04-29 23:32           ` Jim Blandy
2004-05-01  1:14             ` Joel Brobecker
2004-05-01  4:57               ` Jim Blandy [this message]
2004-05-03 16:25                 ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03 22:15 Andrew Pinski
2004-05-04  0:15 ` Joel Brobecker
2004-05-04  0:18   ` Andrew Pinski
2004-01-02  7:25 Joel Brobecker
2004-01-02 14:18 ` Daniel Jacobowitz
2004-01-03 14:42   ` Joel Brobecker
2004-01-03 16:34     ` Eli Zaretskii
2004-01-03 17:47       ` Joel Brobecker
2004-01-02 14:45 ` Eli Zaretskii
2004-01-05 16:18 ` Andrew Cagney
2004-01-05 19:17   ` Joel Brobecker

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=vt24qr0lpei.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=drow@mvista.com \
    --cc=eliz@elta.co.il \
    --cc=gdb-patches@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