From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: core dump.
Date: Thu, 22 Jan 2004 07:49:02 +1000 [thread overview]
Message-ID: <87k73lug4x.fsf@zip.com.au> (raw)
In-Reply-To: <16397.52459.731364.359708@localhost.localdomain> (Han-Wen Nienhuys's message of "Wed, 21 Jan 2004 01:50:51 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> elapsed time: 0.01 secondsBacktrace:
> In c.ly:
> 2: 0* [determine-split-list #(# # # # ...) #(# # # #)]
> In unknown file:
> ?: 1
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1074493760 (LWP 27557)]
> 0x4002f524 in unmemocar (form=0x4050d7b8, env=0x167f) at eval.c:2246
> (gdb) bt
> #0 0x4002f524 in unmemocar (form=0x4050d7b8, env=0x167f) at eval.c:2246
> #1 0x4002f654 in scm_unmemocopy (x=0x404da7e8, env=0x4050de58) at eval.c:2469
I've seen something like this when an error (an ordinary scheme level
error) occurs in code generated by a procedure->macro. Dunno if
that's what's happening here. Running without --debug normally avoids
the segv (though obviously one can't tell quite where it went wrong).
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-01-21 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 0:50 core dump Han-Wen Nienhuys
2004-01-21 21:49 ` Kevin Ryde [this message]
2004-01-22 12:31 ` Han-Wen Nienhuys
2004-01-22 16:20 ` Dirk Herrmann
2004-01-23 17:40 ` Neil Jerram
2004-01-28 13:52 ` uniform-vector? gives true for list Roland Orre
2004-02-06 20:19 ` Roland Orre
2004-02-18 22:12 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 11:36 core dump Bill Schottstaedt
2004-01-22 22:49 ` Marius Vollmer
2004-01-22 23:16 ` Han-Wen Nienhuys
2004-01-22 23:26 ` Marius Vollmer
2004-01-26 11:22 ` Bill Schottstaedt
2004-02-18 21:16 ` Marius Vollmer
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=87k73lug4x.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).