From: John Williams <jwilliams@itee.uq.edu.au>
To: insight@sources.redhat.com
Subject: duplicated source file names
Date: Thu, 14 Aug 2003 06:59:00 -0000 [thread overview]
Message-ID: <3F3B355C.5040904@itee.uq.edu.au> (raw)
Hi,
Debugging a linux kernel, there are many instances where source files of
the same name but different in directories exist - for example super.c
appears in several of the filesystem subdirectories.
However, when debugging this in insight, it only seems to be able to
"recognise" one instance of a particular filename. So, even though I
type in the name of a function in the function drop down
"ext2_read_super", which exists in fs/ext2/super.c, Insight displays the
file /fs/super.c.
This is all on gdb5.0 under RH linux (but also same under Cygwin).
Is this a known issue? IS there a way I can qualify the function name
(or indeed source file) to specify *which* super.c it should find a
function in?
Thanks,
John
next reply other threads:[~2003-08-14 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 6:59 John Williams [this message]
2003-08-14 16:02 ` Keith Seitz
2003-08-14 21:52 ` John Williams
2003-08-14 23:28 ` Keith Seitz
2003-08-14 23:35 ` John Williams
2003-08-14 23:42 ` Keith Seitz
2003-08-15 15:52 ` Andrew Cagney
2003-08-16 18:46 ` Tom Tromey
2003-08-18 16:03 ` Steve Morgan
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=3F3B355C.5040904@itee.uq.edu.au \
--to=jwilliams@itee.uq.edu.au \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).