Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: info sources regression with dwarf2/stabs
Date: Sat, 12 Jun 2004 02:14:00 -0000	[thread overview]
Message-ID: <20040612021445.GA15520@white> (raw)
In-Reply-To: <20040611183510.GB15256@white>

On Fri, Jun 11, 2004 at 02:35:10PM -0400, Bob Rossi wrote:
> On Fri, Jun 11, 2004 at 02:29:16PM -0400, Bob Rossi wrote:
> > Hi,
> > 
> > A user of -file-list-exec-source-files noticed that this command does
> > not initially list the files that are in a library. For example,
> > 
> > I have
> >    $ ls
> >    Makefile  lib.c  lib.h  lib.o  libmilib.a  main  main.c
> > 
> > And
> >    $ cat Makefile
> >    all:
> >       gcc -c -g -Wall lib.c
> >       ar cru libmilib.a lib.o
> >       gcc -g -Wall main.c -o main -L. -lmilib -I.
> > 
> > When I do -file-list-exec-source-files originally, it doesn't show
> > lib.c, after I do 'list lib.c:1' it will then show the filename. Also, I
> > believe it shows all of the filenames in the library. 
> > 
> > My question is, is there any way to get this funcionality from the get
> > go? Load the psymtabs for all the libraries?
> > 
> > Or is there a GDB command that forces loading all symbols into the
> > partial symbol table at start?
> 
> Unfortunatly, I forgot to add one thing. The files from all libraries do
> show up when the stabs debugging format is used. It seems like this is a
> dwarf2 problem. Anyone know if this is a bug?
> 
> Or something maybe I could look into?

Finally, this is also a problem with the 'info sources' command. Does
that make the problem a little more interesting to anyone? :)

Bob Rossi


  reply	other threads:[~2004-06-12  2:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 18:29 -file-list-exec-source-files && libraries Bob Rossi
2004-06-11 18:35 ` Bob Rossi
2004-06-12  2:14   ` Bob Rossi [this message]
2004-06-15 13:51     ` info sources regression with dwarf2/stabs Bob Rossi
2004-06-15 22:53   ` -file-list-exec-source-files && libraries Jim Blandy

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=20040612021445.GA15520@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