From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile 2.2 TODO
Date: Tue, 17 Sep 2013 22:16:49 +0200 [thread overview]
Message-ID: <87hadjryoe.fsf@pobox.com> (raw)
In-Reply-To: <87d2obo6o2.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 14 Sep 2013 15:48:45 +0200")
On Sat 14 Sep 2013 15:48, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> skribis:
>
>> - Add machinery to (system vm debug) to get a DIE for a procedure, if
>> it is present.
>
> It would be great if it would support .gnu_debuglink too (info "(gdb)
> Separate Debug Files").
The guile-dltools stuff does support this, so it should be possible.
Initially I think it makes sense to include it in the .go directly
though, and add things incrementally.
> Another thing I noticed is that in 2.0 we have location info for code,
> but not for (global) variable definitions in general (which prevents
> M-. from doing anything useful for non-procedure top-level variables.)
>
> How would that work with DWARF?
It could work! Currently M-. just fails if the thing isn't a
procedure. But this info could go in the DIE. What would it be
associated with, however? The scoped name or the variable object?
Anyway we can make this happen.
> Personally I’m still very much on the Guix (dark?) side of things, but
> I’d like to get on the 2.1 train sometime in the coming months.
Cool. Happy hacking :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-09-17 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 11:03 Guile 2.2 TODO Andy Wingo
2013-09-01 19:07 ` Peter TB Brett
2013-09-02 20:01 ` Andy Wingo
2013-09-14 13:48 ` Ludovic Courtès
2013-09-17 20:16 ` Andy Wingo [this message]
2013-10-03 21:27 ` Andy Wingo
2013-10-18 9:56 ` Andy Wingo
2013-10-29 12:27 ` Ludovic Courtès
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=87hadjryoe.fsf@pobox.com \
--to=wingo@pobox.com \
--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).