From: Bruce Korb <bkorb@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: (ice-9 debug) is deprecated.
Date: Mon, 09 Apr 2012 13:00:39 -0700 [thread overview]
Message-ID: <4F833FE7.9030909@gnu.org> (raw)
In-Reply-To: <87obr0erv7.fsf@gnu.org>
Hi Ludovic,
On 04/09/12 10:29, Ludovic Courtès wrote:
>> Is this the currently accepted way of setting up an
>> environment where I can trace errors back to their source?
>
> Currently uncaught errors lead to Guile printing a backtrace, normally.
> Doesn’t it work for you?
The honest truth? I found I had to go through this rigmarole to get
error info and file/line info way back when and haven't looked back.
If it is now the default to print out the problem at issue and the
file and line for where the problem was discovered, then I can
remove it. I _would_ prefer to do that, but otherwise I need to do
what I can to get the file/line information. So, can I eliminate
this stuff and still get what I need?
Thank you!! Regards, Bruce
next prev parent reply other threads:[~2012-04-09 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 18:31 (ice-9 debug) is deprecated Bruce Korb
2012-04-07 21:16 ` Ludovic Courtès
2012-04-08 16:14 ` Bruce Korb
2012-04-09 17:29 ` Ludovic Courtès
2012-04-09 20:00 ` Bruce Korb [this message]
2012-04-09 20:44 ` Andy Wingo
2012-04-09 21:24 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F833FE7.9030909@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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).