From: rm@fabula.de
Subject: Segfaults when using readline ...
Date: Thu, 15 Aug 2002 10:19:13 +0200 [thread overview]
Message-ID: <20020815081913.GB8225@www> (raw)
Hello,
my latest compile of guile (checked out from CVS
on Tuseday) segfaults when used with readline activated.
Has anybody experienced this too?
Top of the backtrace is below (any output will trigger
segmentation violation).
Ralf Mattes
ralf@calvin:~$ gdb -q guile
(gdb) r
Starting program: /usr/local/bin/guile
#<directory (guile-user) 8051f30>
guile> (version)guile> (version)^M
Program received signal SIGSEGV, Segmentation fault.
0x4007c049 in sf_fill_input (port=0x40245620) at vports.c:121
121 *pt->read_buf = SCM_CHAR (ans);
(gdb) bt
#0 0x4007c049 in sf_fill_input (port=0x40245620) at vports.c:121
#1 0x40065f14 in scm_fill_input (port=0x40245620) at ports.c:892
#2 0x40065f7a in scm_getc (port=0x40245620) at ports.c:912
#3 0x4006c829 in scm_flush_ws (port=0x40245620, eoferr=0x0) at read.c:188
#4 0x4006c761 in scm_read (port=0x2574) at read.c:155
#5 0x40044703 in scm_deval (x=0x40289688, env=0x40289690) at eval.c:3174
#6 0x4004519d in scm_dapply (proc=0x4028a190, arg1=0x2974, args=0x40289690)
at eval.c:3678
#7 0x4003f984 in scm_apply (proc=0x4028a190, arg1=0x2974, args=0x2974)
at eval.c:3475
#8 0x4003f69c in scm_call_0 (proc=0x4028a190) at eval.c:3329
#9 0x4003516f in scm_dynamic_wind (in_guard=0x4028a1d0, thunk=0x4028a190,
out_guard=0x4028a148) at dynwind.c:128
#10 0x40044703 in scm_deval (x=0x40293568, env=0x4028a228) at eval.c:3174
#11 0x40041f6e in scm_deval (x=0x4028a2e0, env=0x4028a328) at eval.c:2253
#12 0x400436dd in scm_deval (x=0x40250600, env=0x4028a390) at eval.c:2882
#13 0x4004519d in scm_dapply (proc=0x4028a438, arg1=0x2974, args=0x4028a390)
at eval.c:3678
#14 0x40042e82 in scm_deval (x=0x4028a438, env=0x4028a3c8) at eval.c:2637
#15 0x400436dd in scm_deval (x=0x4028a528, env=0x4028a580) at eval.c:2882
#16 0x40045115 in scm_dapply (proc=0x4028a5a8, arg1=0x2974, args=0x4028a580)
at eval.c:3675
#17 0x4003f984 in scm_apply (proc=0x4028a5a8, arg1=0x2974, args=0x2974)
...
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-08-15 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 8:19 rm [this message]
2002-08-15 8:32 ` Segfaults when using readline Han-Wen Nienhuys
2002-08-17 9:49 ` 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=20020815081913.GB8225@www \
--to=rm@fabula.de \
/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).