From: Keith Seitz <keiths@cygnus.com>
To: kyle Loudon <kloudon@matrixsemi.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: Re: Windows Error when I want to start arm-elf-gdb
Date: Tue, 09 Oct 2001 08:15:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112050846140.1739-100000@makita.cygnus.com> (raw)
In-Reply-To: <9DBAD5DD40C5D411BC350002B30275EB4B242C@issus-1.engr.matrixsemi.com>
On Tue, 4 Dec 2001, kyle Loudon wrote:
> I too am running into the same problem as described in the mailing list
> about the Windows error when starting arm-elf-gdb. This is using Insight 5.0
> with the insight-tcl.pat patch applied.
What is "insight-tcl.pat"?
> if {![find_iwidgets_library]} {
> tk_messageBox -title Error -message "Could not find the Iwidgets
> libraries.
> Got nameofexec: [info nameofexecutable]
> Error(s) were: \n$errMsg" \
> -icon error -type ok
> exit
> }
Make sure that errMsg is defined as a global in find_iwidgets_library in
util.tcl. That should at least fix your immediate problem with displaying
the error dialog.
After that, we'll tackle why your copy of Insight cannot find the iwidgets
library...
Keith
WARNING: multiple messages have this Message-ID
From: Keith Seitz <keiths@cygnus.com>
To: kyle Loudon <kloudon@matrixsemi.com>
Cc: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: Re: Windows Error when I want to start arm-elf-gdb
Date: Wed, 05 Dec 2001 08:48:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0112050846140.1739-100000@makita.cygnus.com> (raw)
Message-ID: <20011205084800.Aob8XAApSS0eNvPS1yAlAhon0bqnda5YHh-vIyscM1Q@z> (raw)
In-Reply-To: <9DBAD5DD40C5D411BC350002B30275EB4B242C@issus-1.engr.matrixsemi.com>
On Tue, 4 Dec 2001, kyle Loudon wrote:
> I too am running into the same problem as described in the mailing list
> about the Windows error when starting arm-elf-gdb. This is using Insight 5.0
> with the insight-tcl.pat patch applied.
What is "insight-tcl.pat"?
> if {![find_iwidgets_library]} {
> tk_messageBox -title Error -message "Could not find the Iwidgets
> libraries.
> Got nameofexec: [info nameofexecutable]
> Error(s) were: \n$errMsg" \
> -icon error -type ok
> exit
> }
Make sure that errMsg is defined as a global in find_iwidgets_library in
util.tcl. That should at least fix your immediate problem with displaying
the error dialog.
After that, we'll tackle why your copy of Insight cannot find the iwidgets
library...
Keith
next prev parent reply other threads:[~2001-12-05 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 7:55 kyle Loudon
2001-10-09 8:02 ` Fernando Nasser
2001-12-05 6:51 ` Fernando Nasser
2001-10-09 8:15 ` Keith Seitz [this message]
2001-12-05 8:48 ` Keith Seitz
2001-12-04 16:01 ` kyle Loudon
-- strict thread matches above, loose matches on Subject: below --
2001-10-05 18:42 Stephane Aubert
2001-10-07 13:46 ` Alan Lehotsky
2001-10-07 14:33 ` Keith Seitz
2001-12-04 11:13 ` Keith Seitz
2001-12-04 4:55 ` Alan Lehotsky
2001-12-03 8:56 ` Stephane Aubert
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=Pine.GSO.4.33.0112050846140.1739-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=kloudon@matrixsemi.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).