public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	michaelprocop@gmail.com, nobody@sources.redhat.com
Subject: Re: insight/323: executable must be colocated with source
Date: Thu, 21 Feb 2008 00:54:00 -0000	[thread overview]
Message-ID: <20080221005411.28647.qmail@sourceware.org> (raw)

Synopsis: executable must be colocated with source

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Feb 21 00:54:11 2008
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Thu Feb 21 00:54:11 2008
State-Changed-Why:
    There is something else going on. The source does NOT need to be co-located with your executable: gdb (and hence insight) will find your source files from the debug info contained in the executable.
    
    If this mechanism isn't working, you might need to open a console window and use gdb's "dir" command to help it find the source files (sorry, insight currently doesn't have an equivalent command). Type "help dir" for more information on the dir command in gdb.
    
    I hate to say this, but I've just tested this with my local installation (CVS HEAD), and I am unable to reproduce your problem following the procedure you've specified.
    
    Have you tried using the "-nx" option to gdb/insight? Perhaps there is some stale information in .gdbtkinit?

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=323


             reply	other threads:[~2008-02-21  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  0:54 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-12 14:03 michaelprocop

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=20080221005411.28647.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=michaelprocop@gmail.com \
    --cc=nobody@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).