From: szgyg <szgyg@ludens.elte.hu>
To: John Cowan <cowan@ccil.org>
Cc: 39118@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
guile-devel@gnu.org
Subject: bug#39118: Segfault while building on 64-bit Cygwin
Date: Mon, 3 Feb 2020 23:11:38 +0100 [thread overview]
Message-ID: <20200203221137.GB1659@dtk> (raw)
In-Reply-To: <CAD2gp_SnY-vP03psw4wNDyH-CrbpSZy7ttb-Z0koYOmu5r2VJg@mail.gmail.com>
On Fri, Jan 31, 2020 at 09:23:19AM -0500, John Cowan wrote:
> Aaaand... Cygwin doesn't do core dumps. Under the skin it's WIndows, after
> all. This is what I get when I specify ulimit -c unlimited and rebuild:
> [...]
Please see my previous mail on how to get a real core dump on cygwin
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39118#28
>> On Sat, Jan 25, 2020 at 8:51 AM Ludovic Courtès <ludo@gnu.org> wrote:
>>
>>> That I understand. However, I was asking for the backtrace of the crash
>>> on Cygwin when JIT is enabled. Could you grab it?
#v+
BOOTSTRAP GUILEC ice-9/eval.go
BOOTSTRAP GUILEC ice-9/psyntax-pp.go
BOOTSTRAP GUILEC language/cps/intmap.go
BOOTSTRAP GUILEC language/cps/intset.go
BOOTSTRAP GUILEC language/cps/graphs.go
BOOTSTRAP GUILEC ice-9/vlist.go
BOOTSTRAP GUILEC srfi/srfi-1.go
Thread 1 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 7444.0x2640]
0x000000055a8b1b25 in scm_to_uint64 (val=val@entry=0xffffffffffffff90) at ../../guile-3.0.0/libguile/conv-uinteger.i.c:44
44 else if (SCM_BIGP (val))
(gdb) bt
#0 0x000000055a8b1b25 in scm_to_uint64 (val=val@entry=0xffffffffffffff90) at ../../guile-3.0.0/libguile/conv-uinteger.i.c:44
#1 0x000000055a86b1ea in scm_bytevector_copy_x (source=0x700000948620, source_start=0x34964a, target=0x700000907600, target_start=0x2, len=0xffffffffffffff90)
at ../../guile-3.0.0/libguile/bytevectors.c:604
#2 0x00006ffffe743866 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
BOOTSTRAP GUILEC language/tree-il.go
(gdb) bt
#0 0x000000055a8b1b25 in scm_to_uint64 (val=val@entry=0xffffffffffffff90)
at ../../guile-3.0.0/libguile/conv-uinteger.i.c:44
#1 0x000000055a86b1ea in scm_bytevector_copy_x (source=0x70000055f160, source_start=0x34964a, target=0x700000808c90,
target_start=0x2, len=0xffffffffffffff90) at ../../guile-3.0.0/libguile/bytevectors.c:604
#2 0x00006ffffe73f936 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
BOOTSTRAP GUILEC language/tree-il/analyze.go
(gdb) bt
#0 0x000000055a8b1b25 in scm_to_uint64 (val=val@entry=0xffffffffffffff90)
at ../../guile-3.0.0/libguile/conv-uinteger.i.c:44
#1 0x000000055a86b1ea in scm_bytevector_copy_x (source=0x700000645160, source_start=0x34964a, target=0x7000008012d0,
target_start=0x2, len=0xffffffffffffff90) at ../../guile-3.0.0/libguile/bytevectors.c:604
#2 0x00006ffffe753fc6 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
^C
#v-
s
next prev parent reply other threads:[~2020-02-03 22:11 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 8:39 GNU Guile 2.9.9 Released [beta] Andy Wingo
2020-01-13 8:44 ` Andy Wingo
2020-01-13 17:26 ` John Cowan
2020-01-13 23:09 ` bug#39118: " John Cowan
2020-01-20 16:35 ` bug#39118: Segfault while building on 64-bit Cygwin Ludovic Courtès
2020-01-20 16:38 ` John Cowan
2020-01-20 17:22 ` bug#39118: " Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-02-06 10:53 ` Andy Wingo
2020-02-07 4:56 ` Charles Stanhope
2020-02-14 17:46 ` Charles Stanhope
2020-02-15 17:58 ` Marco Atzeri
2020-02-16 23:23 ` Mike Gran
2020-02-16 23:24 ` John Cowan
2020-02-17 1:08 ` Charles Stanhope
2020-02-17 19:27 ` Charles Stanhope
2020-02-17 21:05 ` Andy Wingo
2020-01-21 9:01 ` Ludovic Courtès
2020-01-21 18:40 ` bug#39118: " szgyg
2020-01-21 21:53 ` John Cowan
2020-01-21 21:37 ` John Cowan
2020-01-23 20:35 ` Ludovic Courtès
2020-01-24 14:36 ` John Cowan
2020-01-25 13:51 ` Ludovic Courtès
2020-01-25 15:54 ` John Cowan
2020-01-31 14:23 ` bug#39118: " John Cowan
2020-02-03 22:11 ` szgyg [this message]
2020-02-05 21:11 ` John Cowan
2020-02-05 22:42 ` szgyg
2020-01-13 21:32 ` GNU Guile 2.9.9 Released [beta] Stefan Israelsson Tampe
2020-01-13 21:33 ` Stefan Israelsson Tampe
2020-01-14 9:57 ` Stefan Israelsson Tampe
2020-01-14 11:16 ` Andy Wingo
[not found] ` <CAGua6m3+mL-1mq0iot1+xvkgkC-_jnhX03uGpOxQkwk0iv12Vw@mail.gmail.com>
2020-01-14 11:43 ` Fwd: " Stefan Israelsson Tampe
2020-01-14 12:18 ` Mikael Djurfeldt
2020-01-14 13:25 ` Stefan Israelsson Tampe
2020-01-14 14:32 ` Andy Wingo
2020-01-14 14:47 ` Stefan Israelsson Tampe
2020-01-14 16:15 ` Andy Wingo
2020-01-14 16:36 ` Stefan Israelsson Tampe
2020-01-14 17:56 ` Stefan Israelsson Tampe
2020-01-14 16:03 ` Mikael Djurfeldt
[not found] ` <CAGua6m2cm2iFTf6EB4MuDR4qNDJ1kt1EjwRCBgLKS+qxncxp+w@mail.gmail.com>
2020-01-14 16:36 ` Fwd: " Stefan Israelsson Tampe
2020-01-14 16:47 ` Mikael Djurfeldt
2020-01-14 17:21 ` Taylan Kammer
2020-01-14 17:27 ` Stefan Israelsson Tampe
2020-01-14 20:54 ` Andy Wingo
2020-01-14 20:13 ` Stefan Israelsson Tampe
2020-01-14 21:17 ` Andy Wingo
2020-01-14 21:48 ` Stefan Israelsson Tampe
2020-01-15 19:58 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2020-01-24 15:26 bug#39118: Segfault while building on 64-bit Cygwin dsmich
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=20200203221137.GB1659@dtk \
--to=szgyg@ludens.elte.hu \
--cc=39118@debbugs.gnu.org \
--cc=cowan@ccil.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).