Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: David Lecomber <david@streamline-computing.com>, gdb@sources.redhat.com
Subject: Re: whodunnit?  info sources now returns duplicates
Date: Wed, 15 Sep 2004 22:11:00 -0000	[thread overview]
Message-ID: <vt27jqvqj3y.fsf@zenia.home> (raw)
In-Reply-To: <20040915181008.GA14735@nevyn.them.org>


Daniel Jacobowitz <drow@false.org> writes:
> On Wed, Sep 15, 2004 at 11:14:56AM +0100, David Lecomber wrote:
> > This is a regression bug -- the version I have tested this are 
> > from CVS on 2004-08-17, and 2004-06-22.  
> > 
> > Any test program:
> > 
> > foo/test.c
> > 
> > int main() {
> > 	int x;
> > }
> > 
> > now compile - but in the directory above foo.
> > 
> > gcc -g foo/test.c
> > 
> > run gdb ./a.out 
> > 
> > For 20040622, only foo/test.c is listed in info sources (correct)
> > For 20040817 (and recent 20040913) foo/test.c and test.c are listed..
> > (incorrect)
> > 
> > When you add a breakpoint to main, and do info sources, the duplicate
> > vanishes..
> > 
> > Any takers?
> 
> Joel's patch to dwarf2read to create symtabs based on the line table
> also creates symtabs if the name of the compilation unit and the name
> in the line table don't match.  I noticed this last week and don't know
> what to do about it.
> 
> One workaround is a patch I whipped together to display the fullname in
> info sources output (arguably more useful anyway).  The two will have
> the same fullnames and we already have code to suppress printing the
> duplicates.  Attached.
> 
> What do you think?

Looks good to me.  If you've tested it, go ahead and commit.



  reply	other threads:[~2004-09-15 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 10:12 David Lecomber
2004-09-15 17:49 ` Andrew Cagney
2004-09-15 18:10 ` Daniel Jacobowitz
2004-09-15 22:11   ` Jim Blandy [this message]
2004-09-16 16:26     ` Andrew Cagney

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=vt27jqvqj3y.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=david@streamline-computing.com \
    --cc=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