public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: pooja nagpal <pooja.nagpal1619@gmail.com>
Cc: insight@sources.redhat.com
Subject: Re: source code query
Date: Tue, 08 Sep 2009 15:01:00 -0000	[thread overview]
Message-ID: <4AA6718B.4030501@redhat.com> (raw)
In-Reply-To: <74903b8c0908070548r3ca3608dv5d03a5475a749594@mail.gmail.com>

On 08/07/2009 05:48 AM, pooja nagpal wrote:
> Insight sometimes cannot find the source code.
> We believe this is due to a windows environment variable being set
> incorrectly, but we do not fully understand the issue or why it seems
> to differ between users.

What makes you believe that a Windows environment variable would alter 
the way gdb or Insight work? To the best of my knowledge, environment 
variables do not affect gdb's or Insight's ability to find source files 
(or do just about anything else).

The first thing to check is if gdb can find your source file (if Insight 
cannot). Open a console window and type "list" (if you want the current 
source location). If gdb outputs an error saying that it cannot find 
your source, you probably need to set the source code search directory 
path. Type "help dir" in a console window to see how to do this.

I am, of course, assuming that all your object files were compiled with 
debug info. If they weren't, there is no way gdb or Insight could find 
them. [I know, that's a really dumb thing to say, but it happens so 
frequently, that I have to mention it.]

Keith

  reply	other threads:[~2009-09-08 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 12:48 pooja nagpal
2009-09-08 15:01 ` Keith Seitz [this message]
2009-09-09  9:35 ` pooja nagpal
2009-09-09 14:51   ` Keith Seitz

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=4AA6718B.4030501@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=pooja.nagpal1619@gmail.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).