unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: mhw@netris.org
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Entering the interactive debugger
Date: Fri, 05 Sep 2014 09:57:38 -0400	[thread overview]
Message-ID: <87fvg6186l.fsf@netris.org> (raw)
In-Reply-To: <CAELgYhfwX3i738WFUuJbGTK9oohfbKzxUiwmYjezxbryiuukGw@mail.gmail.com> (Carlos Pita's message of "Tue, 2 Sep 2014 23:08:26 -0300")

Carlos Pita <carlosjosepita@gmail.com> writes:

> Thank you very much, Dave!
>
>> Couldn't you just use (error)?  It will enter the debugger if run from
>
> I'm doing exactly that, but then there is the limitation that this
> would be postmortem debugging and sometimes I want to suspend
> execution, examine the environment, and *resume* execution.

You can set breakpoints using the ",break" or ",break-at-source" REPL
commands.  See ",help debug" for more info.

For now, to achieve the effect you desire, you could create a procedure
that simply returns the value of some global variable.  Set a breakpoint
on that procedure, and then use that procedure as your "enter debugger"
procedure.  If you want it to resume execution, set the global to your
desired value and continue.

I agree that it would be nice to include a procedure in Guile that does
this more nicely.

      Mark



      reply	other threads:[~2014-09-05 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 19:03 Entering the interactive debugger Carlos Pita
2014-09-02 19:20 ` Thompson, David
2014-09-02 19:57   ` Thompson, David
2014-09-02 20:14   ` Taylan Ulrich Bayirli/Kammer
2014-09-03  2:08     ` Carlos Pita
2014-09-05 13:57       ` mhw [this message]

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=87fvg6186l.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=carlosjosepita@gmail.com \
    --cc=guile-user@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).