Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: duplicate entries in -file-list-exec-source-files
Date: Wed, 25 Feb 2004 03:44:00 -0000	[thread overview]
Message-ID: <20040225034448.GA19094@white> (raw)

Hi,

When I do

gdb -i=mi ./gdb
-file-list-exec-source-files

I get 1242 output entries that contain the fullname field.
If I run that output through sort and uniq, I get 661 fullname fields.
This means that -file-list-exec-source-files is outputting a lot of
duplicates, almost on the ratio of 2 to 1. Most of the duplicates seem
to be header files. Does GDB create a psymtab for each header, every time
it's included into a different file?

Should I handle duplicate output internal to GDB? Or let the front end
deal with it? 

I am thinking GDB should deal with it. Is there an ADT that GDB contains that 
I would be able to create upon entrance of my function, add an entry to the ADT 
each time I output a new filename/fullname pair, then delete the ADT
when I exit my function? If this data type existed, I could easily
suppress duplicating output.

Thanks,
Bob Rossi


                 reply	other threads:[~2004-02-25  3:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040225034448.GA19094@white \
    --to=bob@brasko.net \
    --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