From: Keith Seitz <keiths@redhat.com>
To: yunlu liu <lyunlu@gmail.com>
Cc: insight@sources.redhat.com
Subject: Re: can't open file in Insight
Date: Mon, 16 Nov 2009 22:17:00 -0000 [thread overview]
Message-ID: <4B01CF4A.1090201@redhat.com> (raw)
In-Reply-To: <5d96e8200911161412w6d5eec25w1b99fa5694643819@mail.gmail.com>
On 11/16/2009 02:12 PM, yunlu liu wrote:
> Hi Keith,
> Thanks for your email.I try to just enter the filename in the
> console. It shows "undefined command". I try "help dir" and use the dir
> command. No results are shown.I also have no idea how to display the .c
> file. I wonder if I could read and complile the .c file via
> insight.Looking forward to your reply and thanks a lot for your
> consideration:)
I hate to ask this, but I feel compelled. Are you compiling your
application with debug info? That's the "-g" option to gcc? [Assuming
your using gcc, of course.] Insight/gdb should be able to automatically
locate your source files if you do.
To use the dir command:
If you source file lives in "/this/is/where/it/is/myfile.c", open the
console window and type:
(gdb) dir /this/is/where/it/is
That's it. Insight will remember this the next time you start. To see
the change immediately, change the display mode of the source window
from "SOURCE" to anything (like ASSEMBLY) and then back to "SOURCE". I
believe that should do it.
Keith
next prev parent reply other threads:[~2009-11-16 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 21:09 yunlu liu
2009-11-16 21:25 ` Keith Seitz
2009-11-16 21:46 ` yunlu liu
2009-11-16 21:54 ` Keith Seitz
[not found] ` <5d96e8200911161412w6d5eec25w1b99fa5694643819@mail.gmail.com>
2009-11-16 22:17 ` Keith Seitz [this message]
2009-11-17 16:52 ` yunlu liu
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=4B01CF4A.1090201@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=lyunlu@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).