From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Stack traces
Date: Wed, 15 Feb 2017 09:36:33 -0600 [thread overview]
Message-ID: <87mvdn4gam.fsf@dustycloud.org> (raw)
In-Reply-To: <87h93wto3y.fsf_-_@gnu.org>
Ludovic Courtès writes:
> Hello,
>
> Cecil McGregor <trailingdots@gmail.com> skribis:
>
>> My first problem lies in the lack of a decent debugger.
>> (I can hear the screams of more enlightened Guilers
>> already!) The stack traces seldom provide filenames
>> and line numbers to hint where a problem might hide.
>> While I've read advice to allow the appearance of
>> filenames/line numbers, I still can't seem to
>> consistently find these in a stack trace.
>>
>> I would really like the filename/line number to appear
>> in a stack trace with the actual source code and not
>> some partially opaque macro expansion.
>
> Could you mock up the stack trace as you would like to see it displayed?
>
> I think it would be helpful because what you write here is a common
> complaint, but it’s also something that seasoned Guilers no longer
> realize because they’re used to it. So a fresh eye on what it should
> look like is great.
>
> There are also deeper technical issues, such as tail calls, but we can
> put them aside for now.
>
> Thanks,
> Ludo’.
One thing that we see requested a lot is how to do the equivalent of:
import pdb
pdb.set_trace()
in python, just dumping something to "trigger" the debugger somewhere.
I seem to remember getting some arcane code to do something similar, but
maybe we can just have a simple invocation that people could put
anywhere. (Amirouche has been raising this one also I think.)
next prev parent reply other threads:[~2017-02-15 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.52572.1487077879.22737.guile-user@gnu.org>
2017-02-14 17:24 ` guile-user Digest, Vol 171, Issue 14 Cecil McGregor
2017-02-14 19:19 ` Christopher Allan Webber
2017-02-14 22:00 ` Amirouche
2017-02-14 22:16 ` Stack traces Ludovic Courtès
2017-02-15 15:36 ` Christopher Allan Webber [this message]
2017-02-16 1:10 ` Matt Wette
2017-02-18 0:13 ` Matt Wette
2017-02-18 15:50 ` Amirouche
2017-02-18 15:53 ` Amirouche
2017-02-18 16:58 ` Matt Wette
2017-02-18 19:59 ` Amirouche
2017-02-18 20:31 ` Matt Wette
2017-02-27 20:23 ` Andy Wingo
2017-02-27 20:40 ` Amirouche
2017-05-18 13:38 ` Christopher Allan Webber
2017-05-19 3:05 ` Matt Wette
2017-05-19 9:17 ` Andy Wingo
2017-06-10 9:58 ` Catonano
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=87mvdn4gam.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-user@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).