From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: autocompilation support in master
Date: Thu, 11 Jun 2009 22:50:03 +0100 [thread overview]
Message-ID: <8763f2l9tg.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3vdn52iji.fsf@pobox.com> (Andy Wingo's message of "Tue\, 09 Jun 2009 23\:39\:45 +0200")
Andy Wingo <wingo@pobox.com> writes:
> On Tue 09 Jun 2009 20:47, Mark H Weaver <mhw@netris.org> writes:
>
>> To generate the backtrace, I added the following lines near the top of
>> guile-tools. Is there a better way?
>>
>> (debug-enable 'debug)
>> (debug-enable 'backtrace)
>> (debug-set! depth 100)
>> (write (debug-options-interface))
>> (newline)
>
> No, this is the best way we have currently. As I understand it, the
> debugging evaluator is slower than the normal one -- but at this point,
> who cares? With the VM we are already faster and we keep backtraces. We
> should have backtraces on, always.
>
> Does anyone have objections to that? If not, I'll make that change
> within the week.
Sorry, but I'm not clear what change you're proposing here.
Neil
next prev parent reply other threads:[~2009-06-11 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 22:07 autocompilation support in master Andy Wingo
2009-06-05 22:12 ` Neil Jerram
2009-06-05 22:15 ` Neil Jerram
2009-06-08 23:24 ` Neil Jerram
2009-06-09 0:52 ` Mark H Weaver
2009-06-09 7:27 ` Andy Wingo
2009-06-09 18:47 ` Mark H Weaver
2009-06-09 21:39 ` Andy Wingo
2009-06-10 2:39 ` Mark H Weaver
2009-06-11 21:50 ` Neil Jerram [this message]
2009-06-10 3:39 ` Mark H Weaver
2009-06-10 4:11 ` Mark H Weaver
2009-06-10 4:29 ` Mark H Weaver
2009-06-11 22:23 ` Neil Jerram
2009-06-09 10:31 ` dsmich
2009-06-06 13:19 ` Ludovic Courtès
2009-06-06 23:43 ` Andy Wingo
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=8763f2l9tg.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).