unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: Anyone relying on "break-at" breakpoints?
Date: Fri, 26 Oct 2007 14:10:59 +0200	[thread overview]
Message-ID: <87zly613fw.fsf@laas.fr> (raw)
In-Reply-To: <874pgej3r1.fsf@ossau.uklinux.net> (Neil Jerram's message of "Thu\, 25 Oct 2007 22\:14\:42 +0100")

Hi Neil,

Disclaimer: I'm not too familiar with the debugging infrastructure and
I've never used `break-at'.  But...

Neil Jerram <neil@ossau.uklinux.net> writes:

> By way of contrast, the other kind of breakpoint ("break-in") does not
> suffer from this problem, because it is defined in a way that relates
> more persistently to the code (even as the code changes).  A break-in
> breakpoint is defined as
>
>   break-in <procedure-name> [<module-or-file-name>]
>
> and means break at the start of that procedure.

That looks nice (I suppose it could also perform better than
`scan-source-whash'), but would "let" count as a <procedure-name> in
your example?  If so, how could we specify the scope referred to?

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2007-10-26 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 21:14 Anyone relying on "break-at" breakpoints? Neil Jerram
2007-10-26 12:10 ` Ludovic Courtès [this message]
2007-10-26 18:26   ` Neil Jerram
2007-10-27  9:33     ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2007-10-28 20:54 Neil Jerram
2007-10-28 20:57 ` Neil Jerram
2007-10-28 21:24 ` Neil Jerram
2007-10-29  8:45   ` 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=87zly613fw.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-user@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).