public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: jwilliams@itee.uq.edu.au
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: duplicated source file names
Date: Thu, 14 Aug 2003 16:02:00 -0000	[thread overview]
Message-ID: <1060877014.1578.17.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3F3B355C.5040904@itee.uq.edu.au>

On Thu, 2003-08-14 at 00:08, John Williams wrote:

> 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 a pretty well-known issue for me... I still have nightmares
about it. The problem is not really insight, as I recall. Here's how to
check:

Try a couple of things. Open a console window and enter the commands:

- "list ext2_read_super": Does it return the correct source?
- "info func ext2_read_super": Right info?
- "tk gdbtk_loc ext_read_super": Right info?

Send results to the list. I'm pretty sure that gdb is failing on this,
but it has been a while, and maybe they fixed it and Insight is behind
the times.

BTW, gdb/insight 5.0 is WAY old... Even if it is a gdb problem, I doubt
you're going to get much help with a release that several years old.

Keith


  reply	other threads:[~2003-08-14 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14  6:59 John Williams
2003-08-14 16:02 ` Keith Seitz [this message]
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=1060877014.1578.17.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=jwilliams@itee.uq.edu.au \
    /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).