From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>,
susan@smacchia.net, gdb@sourceware.org
Subject: Re: MI: -file-list-exec-source-files
Date: Sun, 04 Jun 2006 03:34:00 -0000 [thread overview]
Message-ID: <uy7wdbnm3.fsf@gnu.org> (raw)
In-Reply-To: <20060603223537.GA3482@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 3 Jun 2006 18:35:37 -0400)
> Date: Sat, 3 Jun 2006 18:35:37 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, susan@smacchia.net, jimb@codesourcery.com,
> gdb@sourceware.org
>
> > > 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. But it sounds
> like the ones you're observing are the result of a bug.
If the duplicates are due to a bug, then we should fix the bug.
Otherwise, the only way not to have the duplicates is to detect them
and remove them.
FWIW, GDB 6.3 doesn't seem to have this problem, AFAICS:
eliz@fencepost:~$ ./gdb-6.3/gdb/gdb --interpreter=mi2 ./mytest
~"GNU gdb 6.3\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and you are\n"
~"welcome to change it and/or distribute copies of it under certain conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB. Type \"show warranty\" for details.\n"
~"This GDB was configured as \"i686-pc-linux-gnu\"..."
~"Using host libthread_db library \"/lib/tls/libthread_db.so.1\".\n"
~"\n"
(gdb)
-file-list-exec-source-files
^done,files=[{file="crtn.S"},{file="/build/buildd/glibc-2.3.2.ds1/build-tree/i386-libc/csu/crtn.S"},{file="myproc.c",fullname="/home/e/eliz/myproc.c"},{file="mytest.c",fullname="/home/e/eliz/mytest.c"},{file="crti.S"},{file="/build/buildd/glibc-2.3.2.ds1/build-tree/i386-libc/csu/crti.S"},{file="init.c"},{file="start.S"},{file="../sysdeps/i386/elf/start.S"}]
next prev parent reply other threads:[~2006-06-04 3:34 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
2006-06-04 2:50 ` Daniel Jacobowitz
2006-06-04 3:34 ` Eli Zaretskii [this message]
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=uy7wdbnm3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
--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