From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
susan@smacchia.net, jimb@codesourcery.com, gdb@sourceware.org
Subject: Re: MI: -file-list-exec-source-files
Date: Sun, 04 Jun 2006 00:04:00 -0000 [thread overview]
Message-ID: <17538.9045.370853.784139@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060603223537.GA3482@nevyn.them.org>
> > > As you see, there are two entries for myproc.c and two entries for
> > > mytest.c, one with a NULL dirname, the other with a non-NULL dirname.
> >
> > Yes, I can see the duplicate entries
>
> But Eli's got a good point: the one with a NULL dirname is at best
> sub-optimal.
Can we just remove that one then?
> > > Sounds like we should implement duplicate removal from the UI lists?
> >
> > I'm not sure. It may take GDB longer to remove the duplicate entries than
> > it does for Emacs to read them. It would be best not to create them in the
> > first place, but maybe that's not easily done.
>
> There are two potential sources of duplication: bugs, e.g. in our
> processing of symbol vs. line information, and actual duplicate entries
> in the debug info. As Susan correctly noted, the duplicates are often
> legitimate and discarding them entirely would be bad.
OK, I didn't realise that. How do we distinguish between these and those
which aren't needed? Will the legitimate ones always have a non-NULL dirname
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-06-04 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1149277048.21408.ezmlm@sourceware.org>
2006-06-02 23:31 ` susan
2006-06-03 0:05 ` Jim Blandy
2006-06-03 0:46 ` Susan Macchia
2006-06-03 1:28 ` Nick Roberts
2006-06-03 9:46 ` Eli Zaretskii
2006-06-03 22:26 ` Nick Roberts
2006-06-03 22:35 ` Daniel Jacobowitz
2006-06-04 0:04 ` Nick Roberts [this message]
2006-06-04 2:50 ` Daniel Jacobowitz
2006-06-04 3:34 ` Eli Zaretskii
2006-06-06 8:01 ` Nick Roberts
2006-06-03 1:39 ` Bob Rossi
2006-06-02 0:30 Nick Roberts
2006-06-02 19:37 ` Jim Blandy
2006-06-02 19:38 ` Bob Rossi
2006-06-02 20:24 ` Daniel Jacobowitz
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=17538.9045.370853.784139@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=susan@smacchia.net \
/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