From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@streamline-computing.com>
Cc: gdb@sources.redhat.com
Subject: Re: whodunnit? info sources now returns duplicates
Date: Wed, 15 Sep 2004 18:10:00 -0000 [thread overview]
Message-ID: <20040915181008.GA14735@nevyn.them.org> (raw)
In-Reply-To: <1095243296.24882.5.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com>
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?
--
Daniel Jacobowitz
Index: gdb/symtab.c
===================================================================
RCS file: /cvs/src/src/gdb/symtab.c,v
retrieving revision 1.136
diff -u -p -r1.136 symtab.c
--- gdb/symtab.c 11 Sep 2004 10:24:51 -0000 1.136
+++ gdb/symtab.c 14 Sep 2004 23:35:12 -0000
@@ -69,7 +69,7 @@ static void variables_info (char *, int)
static void sources_info (char *, int);
-static void output_source_filename (char *, int *);
+static void output_source_filename (const char *, int *);
static int find_line_common (struct linetable *, int, int *);
@@ -2622,7 +2622,7 @@ filename_seen (const char *file, int add
NAME is the name to print and *FIRST is nonzero if this is the first
name printed. Set *FIRST to zero. */
static void
-output_source_filename (char *name, int *first)
+output_source_filename (const char *name, int *first)
{
/* Since a single source file can result in several partial symbol
tables, we need to avoid printing it more than once. Note: if
@@ -2671,7 +2671,8 @@ sources_info (char *ignore, int from_tty
first = 1;
ALL_SYMTABS (objfile, s)
{
- output_source_filename (s->filename, &first);
+ const char *fullname = symtab_to_fullname (s);
+ output_source_filename (fullname ? fullname : s->filename, &first);
}
printf_filtered ("\n\n");
@@ -2682,7 +2683,8 @@ sources_info (char *ignore, int from_tty
{
if (!ps->readin)
{
- output_source_filename (ps->filename, &first);
+ const char *fullname = psymtab_to_fullname (ps);
+ output_source_filename (fullname ? fullname : ps->filename, &first);
}
}
printf_filtered ("\n");
next prev parent reply other threads:[~2004-09-15 18:10 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 [this message]
2004-09-15 22:11 ` Jim Blandy
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=20040915181008.GA14735@nevyn.them.org \
--to=drow@false.org \
--cc=david@streamline-computing.com \
--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