chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] pressed Ctrl-\ and got segmentation fault


From: Moritz Wilhelmy
Subject: Re: [Chicken-users] pressed Ctrl-\ and got segmentation fault
Date: Fri, 21 Jun 2013 10:54:53 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

Hello,

On Tue, Jun 18, 2013 at 09:36:43 +0200, Peter Bex wrote:
> On Tue, Jun 18, 2013 at 12:02:56AM -0500, Daniel Ajoy wrote:
> > 
> > This is my .csirc
> > 
> > (use readline irregex)
> > (current-input-port (make-gnu-readline-port))
> > (gnu-readline-parse-and-bind "set editing-mode vi")
> > (gnu-history-install-file-manager
> >  (string-append (or (get-environment-variable "HOME") ".") 
> >  "/.chicken_history")
> >  9999)
> > 
> > csi
> > 
> > CHICKEN
> > (c) 2008-2013, The Chicken Team
> > (c) 2000-2007, Felix L. Winkelmann
> > Version 4.8.0.3 (stability/4.8.0) (rev 091c3d9)
> > windows-cygwin-x86 [ manyargs dload ptables ]
> > compiled 2013-03-12 on aeryn.xorinia.dim (Darwin)
> > 
> > I press Ctrl-\
> > 
> > and I get
> > 
> > #;1> ^\Segmentation fault (core dumped)
> > 
> > why?
> 
> Probably because readline is flaky.  Try with parley, which is
> more "native" and supports threading better anyway..

I can confirm that it happens without any readline-ish extensions (and in fact
no ~/.csirc at all). This chicken 4.7.0 is on FreeBSD/amd64 9.1-RELEASE.

It should be noted that ^\ sends SIGQUIT, similar to the way ^C sends SIGINT,
and in fact csi segfaults if I kill -QUIT it as well.


Best regards,

Moritz



reply via email to

[Prev in Thread] Current Thread [Next in Thread]