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

2013-06-24 Thread Christian Kellermann
* Christian Kellermann [130621 11:38]: > Hi Daniel and Moritz, > > * Daniel Ajoy [130618 07:03]: > > > > I press Ctrl-\ > > > > and I get > > > > #;1> ^\Segmentation fault (core dumped) > > > > why? > > This looks like a bug, I have opened ticket 1018 for it. You can > see progress of that

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

2013-06-23 Thread Jim Ursetto
Ah, so the segfault also occurs with plain old `cat` then? I think we can close this bug ;) Thanks for tracking this down further. On Jun 23, 2013, at 7:14, Moritz Wilhelmy wrote: > On 21.06.2013 22:34, John Cowan wrote: >> I can confirm that on 32-bit Linux. On Cygwin, however, typing ^\ doe

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

2013-06-23 Thread Moritz Wilhelmy
On 21.06.2013 22:34, John Cowan wrote: > I can confirm that on 32-bit Linux. On Cygwin, however, typing ^\ does > trigger a SIGSEGV with dumped core (except that it doesn't actually dump > core because the Windows kernel can't do that). Both systems are running > version 4.8.2 (rev ea02c9a), and

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

2013-06-21 Thread John Cowan
Moritz Wilhelmy scripsit: > I misread the problem as "dumps core" rather than "segfaults". > Sorry for the confusion, it exits because of SIGQUIT for me, and dumps > core. It does however not exit because of SIGSEGV. I can confirm that on 32-bit Linux. On Cygwin, however, typing ^\ does trigger

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

2013-06-21 Thread Moritz Wilhelmy
Hello Daniel, On Fri, Jun 21, 2013 at 10:54:53 +0200, Moritz Wilhelmy wrote: > 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

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

2013-06-21 Thread Christian Kellermann
Hi Daniel and Moritz, * Daniel Ajoy [130618 07:03]: > > I press Ctrl-\ > > and I get > > #;1> ^\Segmentation fault (core dumped) > > why? This looks like a bug, I have opened ticket 1018 for it. You can see progress of that issue in the bugtracker at https://bugs.call-cc.org/ticket/1018. Th

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

2013-06-21 Thread Christian Kellermann
* Moritz Wilhelmy [130621 11:30]: > Hello, > > > > 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

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

2013-06-21 Thread Moritz Wilhelmy
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") > > (g

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

2013-06-18 Thread Peter Bex
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 "

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

2013-06-17 Thread Daniel Ajoy
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") ) csi CHICKEN (c) 2008-2013, The Chi