From: Bruce Korb <bkorb@gnu.org>
Cc: Keith Seitz <keiths@redhat.com>, insight@sourceware.org
Subject: Re: Insight won't let me use the source any more
Date: Mon, 23 Jan 2006 00:27:00 -0000 [thread overview]
Message-ID: <43D422F6.40502@gnu.org> (raw)
In-Reply-To: <43D421FC.9040003@gnu.org>
Bruce Korb wrote:
>
> Hi,
>
> Some strange thing has happened and now I cannot get Insight to
> let me do source level debugging any more. I saved aside a version
> of ~/.gdbtkinit, but rewriting it with the saved version and (also)
> deleting it completely accomplishes nothing. Nothing I do brings
> back source level debugging. What's the secret? :) Thanks. - Bruce
>
> $ insight --version
> GNU gdb 6.4.0.20051202-cvs
> <<blah, blah, blah>>
> This GDB was configured as "i686-pc-linux-gnu"
>
/home/bkorb/ag/ag/agen5/autogen.c:2: 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 47)
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
next prev parent reply other threads:[~2006-01-23 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 10:52 Insight crashing when debugging invalid pointers elmer.elmer
2005-11-18 22:36 ` Keith Seitz
2005-11-21 11:53 ` elmer
2006-01-23 0:23 ` Insight won't let me use the source any more Bruce Korb
2006-01-23 0:27 ` Bruce Korb [this message]
2006-01-23 2:43 ` Vale Group
2006-01-23 7:27 ` Bruce Korb
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=43D422F6.40502@gnu.org \
--to=bkorb@gnu.org \
--cc=insight@sourceware.org \
--cc=keiths@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).