From: Andy Wingo <wingo@pobox.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: 23051@debbugs.gnu.org
Subject: bug#23051: segfault in master (2.1)
Date: Mon, 20 Jun 2016 18:19:37 +0200 [thread overview]
Message-ID: <87ziqfesti.fsf@pobox.com> (raw)
In-Reply-To: <07DED91E-09DC-4277-9AA3-7F5C84C30CEB@bluewin.ch> (Daniel Llorens's message of "Fri, 18 Mar 2016 16:35:35 +0100")
On Fri 18 Mar 2016 16:35, Daniel Llorens <daniel.llorens@bluewin.ch> writes:
> The error seems to happen in the error reporting, not actually because of the shift.
>
> The following backtrace is with Guile compiled with -O1 -g, the same error happens with -O2.
>
> GNU Guile 2.1.1.125-ae0380-dirty
> Copyright (C) 1995-2014 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (import (ice-9 control))
> scheme@(guile-user)> (shift k 9)
>
> Thread 1 "guile" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7b3e02a in scm_is_pair (x=0x61900000300) at ../../src4/libguile/pairs.h:159
> 159 return SCM_I_CONSP (x);
> (gdb) backtrace
> #0 0x00007ffff7b3e02a in scm_is_pair (x=0x61900000300) at ../../src4/libguile/pairs.h:159
> #1 scm_iprlist (hdr=<optimized out>, hdr@entry=0x7ffff7b9799d "(", exp=exp@entry=0x7ffff7fb0748, tlr=tlr@entry=41, port=port@entry=0x98b3c0,
> pstate=pstate@entry=0x7e9b00) at ../../src4/libguile/print.c:1427
Still happens on 2.1.3.
next prev parent reply other threads:[~2016-06-20 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 15:35 bug#23051: segfault in master (2.1) Daniel Llorens
2016-06-20 16:19 ` Andy Wingo [this message]
2016-12-01 13:00 ` Daniel Llorens
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=87ziqfesti.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=23051@debbugs.gnu.org \
--cc=daniel.llorens@bluewin.ch \
/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).