From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: [MI] -file-list-exec-source-files
Date: Fri, 13 Feb 2004 01:29:00 -0000 [thread overview]
Message-ID: <20040213012946.GB4476@white> (raw)
Hi,
I have been trying to implement -file-list-exec-source-files for some
time now. So far the command outputs the filename and fullname for each
symtab and psymtab. The fullname part only get's output if GDB knows
what it is.
The problem is, I recently discovered that the fullname can only be
retrieved from the symtab, it can't be retrieved with just a psymtab.
The reason is because the symtab has a 'dirname' member, which is
necessary in finding the absolute path to a source file. Obviously I
can't read in all the symtabs just to get the fullname for each psymtab.
So, I have 2 solutions,
1. Modify the psytmab to also have the 'dirname'. Which seems
difficult. Although I do think this is the best solution. (Not knowing
to much about psymtabs and symtabs)
2. Change -file-list-exec-source-file to receive an optional filename,
which when doing this causes GDB to read in the symtab associated with
the psymtab. Then the fullname can be retrieved.
I believe option 2 is how the CLI works.
If you do
list foo.c:1
info source
I am sure this reads in the symtab for foo.c and then it knows how to
get the fullpath. I don't really like this solution that much, so I
think it would be better to add the 'dirname' to the psymtab.
Any suggestions?
If your interested in poking around to see where symtab->dirname gets
set, look around buildsym.c:975. Does anyone know if there would be an
easy way into getting dirname set into the psymtab?
Thanks,
Bob Rossi
next reply other threads:[~2004-02-13 1:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 1:29 Bob Rossi [this message]
2004-02-16 1:26 ` Bob Rossi
2004-02-16 1:42 ` Kip Macy
2004-02-16 3:19 ` Bob Rossi
2004-02-16 3:30 ` Daniel Jacobowitz
2004-02-16 3:45 ` Bob Rossi
2004-02-16 3:49 ` Daniel Jacobowitz
2004-02-16 15:33 ` Bob Rossi
2004-02-16 15:46 ` Daniel Jacobowitz
2004-02-16 16:08 ` Bob Rossi
2004-02-17 18:22 ` Andrew Cagney
2004-02-17 19:10 ` Bob Rossi
2004-02-17 19:12 ` Daniel Jacobowitz
2004-02-17 19:30 ` Bob Rossi
2004-02-17 19:33 ` Daniel Jacobowitz
2004-02-23 13:13 ` Bob Rossi
2004-02-23 13:55 ` Daniel Jacobowitz
2004-02-24 4:26 ` Bob Rossi
2004-02-27 6:23 ` Bob Rossi
2004-02-27 15:00 ` Daniel Jacobowitz
2004-02-17 19:47 ` Andrew Cagney
2004-02-17 20:02 ` Bob Rossi
2004-02-17 20:27 ` Andrew Cagney
2004-02-17 21:08 ` Bob Rossi
2004-02-17 21:37 ` Daniel Jacobowitz
2004-02-17 21:58 ` Bob Rossi
2004-02-18 14:24 ` Alain Magloire
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=20040213012946.GB4476@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