From: Andrew Burgess <aburgess@redhat.com>
To: Matt Wette <matt.wette@gmail.com>, Guile User <guile-user@gnu.org>
Subject: Re: guile under gdb crashing on Unbuntu 22.04
Date: Fri, 06 May 2022 09:47:20 +0100 [thread overview]
Message-ID: <8735hnm4iv.fsf@redhat.com> (raw)
In-Reply-To: <6c65ce8f-c414-06f6-305c-be5a86aa3629@gmail.com>
Matt Wette <matt.wette@gmail.com> writes:
> Hi All,
>
> I have no clue what is going on here but wondering if others are seeing it.
> I recently installed Ubuntu 22.04, then recompiled guile-3.0.8.
> It crashes running withing gdb, runs fine otherwise:
>
> $ meta/gdb-uninstalled-guile
> GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
> Copyright (C) 2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from
> /home/mwette/proj/guile/guile-3.0.8-build/libguile/.libs/guile...
> (gdb) run
> Starting program:
> /home/mwette/proj/guile/guile-3.0.8-build/libguile/.libs/guile
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7bdd8f2 in GC_find_limit_with_bound () from
> /lib/x86_64-linux-gnu/libgc.so.1
> (gdb) info stack
> #0 0x00007ffff7bdd8f2 in GC_find_limit_with_bound ()
> from /lib/x86_64-linux-gnu/libgc.so.1
This is almost certainly this issue:
https://github.com/ivmai/bdwgc/issues/409
which span out into this issue:
https://github.com/ivmai/bdwgc/issues/432
which was fixed with this commit:
https://github.com/ivmai/bdwgc/commit/8868a7a3cc70e5302f7835a2040a9726238b4f6a
I'm not sure which version of libgc that fix is in though.
Thanks,
Andrew
next prev parent reply other threads:[~2022-05-06 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 12:42 guile under gdb crashing on Unbuntu 22.04 Matt Wette
2022-05-05 15:47 ` Aleix Conchillo Flaqué
2022-05-05 18:48 ` Daniel Tornabene
2022-05-05 19:22 ` Matt Wette
2022-05-06 8:47 ` Andrew Burgess [this message]
2022-05-06 12:32 ` Matt Wette
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=8735hnm4iv.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).