From: Julian Graham <joolean@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: trace examples broken in master
Date: Thu, 9 Jul 2009 15:22:38 -0400 [thread overview]
Message-ID: <2bc5f8210907091222v6d3a3b8cqd91050a02b9d4f9c@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Hi Guilers,
I went to try out some of the traps / tracing features in the debugger
last night, and I ran into some compilation issues with `(ice-9
debugging ice-9-debugger-extensions)'. A patch that resolves them is
attached -- I haven't pushed because I'm not sure I fully understand
the broader context of the code (e.g., why are we checking the version
when the debugger is now part of Guile itself?), and because I'm still
a little git-shy.
More importantly, though, tracing (as per the examples in section
5.21.3.5 of the manual) doesn't seem to produce any output. Not sure
where to look to figure that out.
Regards,
Julian
[-- Attachment #2: 0001-Fix-compilation-issue-in-ice-9-debugger-extensions.patch --]
[-- Type: text/x-patch, Size: 1893 bytes --]
From 8751fedfe28eb94cb2974aeb5a2a08310c03d942 Mon Sep 17 00:00:00 2001
Message-Id: <8751fedfe28eb94cb2974aeb5a2a08310c03d942.1247165262.git.julian.graham@aya.yale.edu>
From: Julian Graham <julian.graham@aya.yale.edu>
Date: Thu, 9 Jul 2009 14:44:53 -0400
Subject: [PATCH] Fix compilation issue in ice-9-debugger-extensions
* module/ice-9/debugging/ice-9-debugger-extensions.scm: Replace `define' in cond expressions.
---
.../ice-9/debugging/ice-9-debugger-extensions.scm | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/module/ice-9/debugging/ice-9-debugger-extensions.scm b/module/ice-9/debugging/ice-9-debugger-extensions.scm
index a8b8c97..df4f4a6 100644
--- a/module/ice-9/debugging/ice-9-debugger-extensions.scm
+++ b/module/ice-9/debugging/ice-9-debugger-extensions.scm
@@ -32,10 +32,10 @@
#:use-module (ice-9 debugger)
#:use-module (ice-9 debugger state)
#:use-module (ice-9 debugging traps))
- (define new-define-command define-command)
- (set! define-command
- (lambda (name argument-template documentation procedure)
- (new-define-command name argument-template procedure))))
+ (let ((new-define-command define-command))
+ (set! define-command
+ (lambda (name argument-template documentation procedure)
+ (new-define-command name argument-template procedure)))))
(else
(define-module (ice-9 debugger))))
@@ -126,8 +126,9 @@ print the result obtained."
(cond ((string>=? (version) "1.7"))
(else
- (define (debugger-command-loop state)
- (read-and-dispatch-commands state (current-input-port)))))
+ (set! debugger-command-loop
+ (lambda (state)
+ (read-and-dispatch-commands state (current-input-port))))))
(define-public (debug-trap trap-context)
"Invoke the Guile debugger to explore the stack at the specified @var{trap}."
--
1.6.0.4
next reply other threads:[~2009-07-09 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 19:22 Julian Graham [this message]
2009-07-14 8:07 ` trace examples broken in master Neil Jerram
2009-07-23 21:42 ` Andy Wingo
2009-08-14 17:00 ` Neil Jerram
2009-08-14 17:21 ` Julian Graham
2009-08-30 10:07 ` Neil Jerram
2009-08-30 15:10 ` Julian Graham
2009-09-01 22:16 ` Neil Jerram
2009-09-15 21:54 ` Neil Jerram
2009-09-16 0:55 ` Neil Jerram
2009-09-22 14:28 ` Julian Graham
2009-09-22 19:57 ` Neil Jerram
2009-09-23 1:34 ` Julian Graham
2009-09-23 20:19 ` Neil Jerram
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=2bc5f8210907091222v6d3a3b8cqd91050a02b9d4f9c@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@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).