unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-user@gnu.org
Subject: setting breakpoints at the repl
Date: Mon, 20 Dec 2021 07:06:07 +0000	[thread overview]
Message-ID: <87zgovrc0w.fsf@gnus.jao.io> (raw)


Hi,

I am working on improving the debugger interface for geiser-guile (the
main idea is to be able to send debugging meta-commands from the 
*Geiser Dbg* buffer... there's something already in there in the HEAD
branches), but i am failing to understand how to set breakpoints at the
source level using ,break-at-source.  Basically, every single time i try
to set one with something like

    ,break-at-source "/home/jao/foo.scm" 3

the REPL tells me back:

    While executing meta-command:
    No procedures found at ~a:~a. "/home/jao/foo.scm" 3

I'm providing line numbers that fall inside procedure definitions (as
advised by the meta-command's doctring), but i'm still getting the same
error, no matter what.  For instance, foo.scm above contains

       (define (foo x)
         (display x)
         (display x)  ;; wanted a bp here
         (display x)
         (display x))

This is Guile 3.0.7, packaged by debian.

I must be missing something obvious, but it's too late to drink more
coffee :) What is it?

Thanks in advance!
jao
-- 
Lisp has assisted a number of our most gifted fellow humans in
thinking previously impossible thoughts. —Edsger Dijkstra




             reply	other threads:[~2021-12-20  7:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20  7:06 Jose A. Ortega Ruiz [this message]
2021-12-25 12:58 ` setting breakpoints at the repl zx spectrumgomas
2021-12-26  1:28   ` Jose Antonio Ortega Ruiz
2021-12-26 22:40 ` Jérémy Korwin-Zmijowski
2021-12-26 23:41   ` Jose A. Ortega Ruiz
2021-12-27  2:42     ` Jose A. Ortega Ruiz
2023-09-20 14:09       ` Mikael Djurfeldt

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=87zgovrc0w.fsf@gnus.jao.io \
    --to=jao@gnu.org \
    --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).