unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Neil Jerram <neiljerram@gmail.com>
Cc: Olivier Dion <olivier.dion@polymtl.ca>,  guile-devel@gnu.org
Subject: Re: A Guile debugger workgroup?
Date: Wed, 01 Mar 2023 10:59:14 -0500	[thread overview]
Message-ID: <87pm9sh38t.fsf@gmail.com> (raw)
In-Reply-To: <CAKuG=vtPLHPsnqFwbqXnQNsjiXPiM_ziyY8hDm8NdqM=RNmE7w@mail.gmail.com> (Neil Jerram's message of "Tue, 29 Nov 2022 17:58:24 +0000")

Hi Neil,

Neil Jerram <neiljerram@gmail.com> writes:

> I wrote something called GDS, back in 1.8 days, that combined some of
> the Emacs interaction features that we now have with Geiser, with
> step-by-step debugging and breakpoints.  You can read about that here:
> https://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/Using-Guile-in-Emacs.html#Using-Guile-in-Emacs

Thanks for sharing; unfortunately the page has vanished, it seems, and I
couldn't find an alternative link.  Is the GDS source still available
from somewhere?  Perhaps it could offer hints about how to integrate
Guile with Emacs.

I'd think the lowest friction, most maintainable way though would be to
ensure that the existing Guile debugger covers all the use cases we want
it to, and then bind it to Emacs using GUD, RealGUD or a similar
existing library.  That way it should be also be possible to use it with
other IDEs, which'd help with democratizing Guile, in my opinion.

> Unfortunately the debugging side of GDS was based on the low level
> traps in the 1.8 interpreter, and that was all blown away in the 2.0
> rewrite, so GDS stopped working at that point.  I don't know what
> modern equivalent 3.x has to the 1.8 low level traps - perhaps we
> would instead advocate for recompiling the relevant code with extra
> instrumentation, like edebug does?

Edebug offers a great debugging experience, so if we can mimic any of
what it does, it'd probably be a good thing!

-- 
Thanks,
Maxim



  reply	other threads:[~2023-03-01 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:21 A Guile debugger workgroup? Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-11-29 17:58 ` Neil Jerram
2023-03-01 15:59   ` Maxim Cournoyer [this message]
2022-11-29 20:18 ` Damien Mattei
2023-03-02  6:18 ` Jannneke Nieuwenhuizen
2023-03-02  7:54   ` Dr. Arne Babenhauserheide
2023-03-03 10:28     ` Janneke Nieuwenhuizen
2023-03-03 10:30       ` Jan Nieuwenhuizen

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=87pm9sh38t.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=neiljerram@gmail.com \
    --cc=olivier.dion@polymtl.ca \
    /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).