From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2744 invoked by alias); 4 Jun 2006 03:34:22 -0000 Received: (qmail 2736 invoked by uid 22791); 4 Jun 2006 03:34:21 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 04 Jun 2006 03:34:20 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-229-13.inter.net.il [80.230.229.13]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id DOM10629 (AUTH halo1); Sun, 4 Jun 2006 06:34:10 +0300 (IDT) Date: Sun, 04 Jun 2006 03:34:00 -0000 Message-Id: From: Eli Zaretskii To: Nick Roberts , susan@smacchia.net, gdb@sourceware.org In-reply-to: <20060603223537.GA3482@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 3 Jun 2006 18:35:37 -0400) Subject: Re: MI: -file-list-exec-source-files Reply-to: Eli Zaretskii References: <20060603004553.33821.qmail@web51812.mail.yahoo.com> <17536.58772.420434.491191@kahikatea.snap.net.nz> <17538.3165.636175.483701@kahikatea.snap.net.nz> <20060603223537.GA3482@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00018.txt.bz2 > Date: Sat, 3 Jun 2006 18:35:37 -0400 > From: Daniel Jacobowitz > Cc: Eli Zaretskii , 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"}]