From: hanwen@byrd.xs4all.nl (Han-Wen Nienhuys)
Subject: Re: No way out.
Date: Sun, 1 Jan 2006 19:58:07 +0000 (UTC) [thread overview]
Message-ID: <dp9c8f$bef$1@sea.gmane.org> (raw)
In-Reply-To: 87hd8pb8o7.fsf@ossau.uklinux.net
In article <87hd8pb8o7.fsf@ossau.uklinux.net>,
Neil Jerram <neil@ossau.uklinux.net> wrote:
>
>> If you intend to look at this, then I can try to isolate it to a
>> smaller case.
>
>Yes, please; I'm keen to understand this. Or I can work from the
>Lilypond code, if you can suggest a point to start from (such as where
>the error occurs that you want backtrace for).
For starters, we could figure out why --debug doesn't work. This is
for a current CVS GUILE
muurbloem:~/src/lilypond$ cat g.scm
(define (f x)
(display "HI")
zapp)
(define (g x)
(x))
(g f)
muurbloem:~/src/lilypond$ guile --debug g.scm
ERROR: Wrong number of arguments to #<procedure f (x)>
muurbloem:~/src/lilypond$ guile g.scm
ERROR: Wrong number of arguments to #<procedure f (x)>
muurbloem:~/src/lilypond$ guile
(guile>
(load "g.scm")
Backtrace:
In unknown file:
?: 0* [primitive-load "g.scm"]
In g.scm:
11: 1* [g #<procedure f (x)>]
7: 2 [f]
g.scm:7:3: In procedure f in expression (x):
g.scm:7:3: Wrong number of arguments to #<procedure f (x)>
ABORT: (wrong-number-of-args)
guile>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-01-01 19:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 0:16 gh_inexact_p error in 1.7.x Bruce Korb
2005-12-01 0:44 ` Kevin Ryde
2005-12-05 4:08 ` No way out Bruce Korb
2005-12-05 4:35 ` Bruce Korb
2005-12-07 1:31 ` Marius Vollmer
2005-12-05 22:20 ` Kevin Ryde
2005-12-06 10:58 ` Han-Wen Nienhuys
2005-12-28 15:59 ` Neil Jerram
2005-12-31 15:09 ` Han-Wen Nienhuys
2005-12-31 15:14 ` Neil Jerram
2006-01-01 19:58 ` Han-Wen Nienhuys [this message]
2006-01-02 15:42 ` Neil Jerram
2006-01-02 18:54 ` Neil Jerram
2006-01-04 21:13 ` Backtrace and enhanced catch Neil Jerram
2006-01-14 12:41 ` Neil Jerram
2006-01-22 13:47 ` Marius Vollmer
2006-01-23 20:11 ` Neil Jerram
2006-01-24 21:34 ` Marius Vollmer
2006-01-16 8:38 ` Ludovic Courtès
2006-01-18 23:08 ` Neil Jerram
2006-01-19 9:38 ` Ludovic Courtès
2006-01-21 11:26 ` Neil Jerram
2006-01-26 23:29 ` Kevin Ryde
2006-01-27 19:30 ` Neil Jerram
2006-01-31 20:07 ` Kevin Ryde
2006-02-01 23:04 ` Neil Jerram
2006-02-04 0:46 ` Kevin Ryde
2006-02-04 15:41 ` Neil Jerram
2005-12-07 1:07 ` No way out Marius Vollmer
2005-12-07 1:55 ` Rob Browning
2005-12-13 20:32 ` Marius Vollmer
2005-12-28 16:09 ` 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='dp9c8f$bef$1@sea.gmane.org' \
--to=hanwen@byrd.xs4all.nl \
--cc=hanwen@xs4all.nl \
/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).