From: Tom Tromey <tromey@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: insight bug
Date: Mon, 27 Nov 2000 19:11:00 -0000 [thread overview]
Message-ID: <87vgt8eq9x.fsf@creche.cygnus.com> (raw)
In-Reply-To: <3A230157.370A41A@cygnus.com>
>> Here's an insight bug: if I introduce a Tcl bug into the insight
>> startup process, I get a blank window but nothing else. It would
>> be nice if Insight fully died and printed the Tcl stack trace to
>> stderr.
Fernando> It would be nice (at least when it is started from a
Fernando> console).
I looked at gdbtk/library/main.tcl and found that I can set
GDBTK_DEBUGFILE to `stdout' or a file name and log messages, including
errors, will go there.
`stderr' doesn't work. Patch to follow shortly.
Tom
next prev parent reply other threads:[~2000-11-27 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-27 16:36 Tom Tromey
2000-11-27 16:40 ` Christopher Faylor
2000-11-27 16:46 ` Tom Tromey
2000-11-27 16:57 ` Fernando Nasser
2000-11-27 17:08 ` Hey, I am back Fernando Nasser
2000-11-27 16:51 ` insight bug Fernando Nasser
2000-11-27 19:11 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-21 15:11 Tom Tromey
2000-04-24 11:07 ` James Ingham
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=87vgt8eq9x.fsf@creche.cygnus.com \
--to=tromey@cygnus.com \
--cc=fnasser@cygnus.com \
--cc=insight@sourceware.cygnus.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).