From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: repl debugger impressions
Date: Sun, 17 Oct 2010 15:10:57 +0200 [thread overview]
Message-ID: <874oclhsm6.fsf@gnu.org> (raw)
In-Reply-To: 519970.1475.qm@web37901.mail.mud.yahoo.com
Hi Mike,
Mike Gran <spk121@yahoo.com> writes:
> -> Step into #<frame a1b2c3d4 #<procedure ...
>
> IMHO, Unless that hex number can be decoded via some command, it
> is just noise.
It’s not just noise because it allows you to distinguish, e.g., between
same-named procedures. As for frame addresses, it allows you to know
whether you’re actually going down the stack or not, for instance (GDB
gives that info too.) So I find it quite valuable.
Now, perhaps it could be formatted in a more human-readable way?
> Also, there is one feature that would make the debugger much
> more valuable to me. If, after every ",step" or ",next", it
> printed out the filename:line:column, that'd be helpful. I
> hacked on it a little, and I think it would be easy to do.
+1
> And, if that filename:line:column were delimited by something
> unique, for example curly braces, it would then be easy enough
> to write an Emacs minor mode to pick up that filename:line:column
> from the Geiser or Shell window and automatically center another
> window on that file at that source line, the way the GDB GUD mode
> does.
+1
I think we need input from the Gesier Meister here. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-10-17 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 19:07 repl debugger impressions Mike Gran
2010-10-17 13:10 ` Ludovic Courtès [this message]
2010-10-17 18:00 ` Jose A. Ortega Ruiz
2010-10-19 18:33 ` 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=874oclhsm6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).