From: yunlu liu <lyunlu@gmail.com>
To: insight@sources.redhat.com
Subject: can't open file in Insight
Date: Mon, 16 Nov 2009 21:09:00 -0000 [thread overview]
Message-ID: <5d96e8200911161308n9e0c2caif70670ef5d1ad949@mail.gmail.com> (raw)
Hi,
I installed insight on Ubuntu9.04. I find I couldn't use the insight
to open *.c files. When I click File->open/source choose a *.c file,
it shows error in sourced command file: undefined command: " ". Try
"help". And the stack trace for error is as follows:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Error in sourced command file:
Undefined command: "". Try "help".
while executing
"gdb_cmd "source $file_name""
(procedure "source_file" line 4)
invoked from within
"source_file"
invoked from within
".srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file
invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tk::MenuInvoke" line 50)
invoked from within
"tk::MenuInvoke
.srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file
1"
(command bound to event)errorCode is NONE
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'm just a beginner of insight. I wonder what the problem is. Looking
forward to replies.Thanks a lot.
--
Best Regards!
next reply other threads:[~2009-11-16 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 21:09 yunlu liu [this message]
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
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=5d96e8200911161308n9e0c2caif70670ef5d1ad949@mail.gmail.com \
--to=lyunlu@gmail.com \
--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).