From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: guile under gdb crashing on Unbuntu 22.04
Date: Thu, 5 May 2022 12:22:58 -0700 [thread overview]
Message-ID: <f66f1b87-e006-52e2-ea02-e1640d681bcf@gmail.com> (raw)
In-Reply-To: <CAMo=-SB3WF4zX_07bUgyRiL7nnoywuxm_B9Kw7a4KTGhC4czOw@mail.gmail.com>
I suspect this is not related to whether guile support is compiled into gdb.
The next step is to get the libgc debug info, to track within that package.
I may do it. If someone wants to take a stab here is info on getting the
debug packages:
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
On 5/5/22 11:48 AM, Daniel Tornabene wrote:
> so, I don't know off the top of my head how Ubuntu does their GDB
> packaging, but Debian does not package GDB with guile support enabled, you
> have to recompile GDB with the configuration option --with-guile and have
> either 2.2.x or 3 installed, along with the appropriate dev packages. I'd
> be willing to bet that this is something to do with that. Maybe check your
> pkg-config options and see what guile is linked with?
>
> On Thu, May 5, 2022 at 10:48 AM Aleix Conchillo Flaqué <aconchillo@gmail.com>
> wrote:
>
>> I'm also on UBuntu 22.04 and happens the same with guile 3.0.7 that comes
>> with it:
>>
>> (gdb) run
>> Starting program: /usr/bin/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.
>> 0x00007ffff7be58f2 in GC_find_limit_with_bound () from
>> /lib/x86_64-linux-gnu/libgc.so.1
>> (gdb) bt
>> #0 0x00007ffff7be58f2 in GC_find_limit_with_bound () from
>> /lib/x86_64-linux-gnu/libgc.so.1
>> #1 0x00007ffff7be59da in GC_init_linux_data_start () from
>> /lib/x86_64-linux-gnu/libgc.so.1
>> #2 0x00007ffff7be6f67 in GC_init () from /lib/x86_64-linux-gnu/libgc.so.1
>> #3 0x00007ffff7eb6c8e in ?? () from
>> /lib/x86_64-linux-gnu/libguile-3.0.so.1
>> #4 0x00007ffff7f1a90f in ?? () from
>> /lib/x86_64-linux-gnu/libguile-3.0.so.1
>> #5 0x00007ffff7f1acde in ?? () from
>> /lib/x86_64-linux-gnu/libguile-3.0.so.1
>> #6 0x00007ffff7be580b in GC_call_with_stack_base () from
>> /lib/x86_64-linux-gnu/libgc.so.1
>> #7 0x00007ffff7f15dbc in scm_with_guile () from
>> /lib/x86_64-linux-gnu/libguile-3.0.so.1
>> #8 0x00007ffff7eb6bd9 in scm_boot_guile () from
>> /lib/x86_64-linux-gnu/libguile-3.0.so.1
>> #9 0x0000555555555193 in ?? ()
>> #10 0x00007ffff7c63d90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
>> #11 0x00007ffff7c63e40 in __libc_start_main () from
>> /lib/x86_64-linux-gnu/libc.so.6
>> #12 0x0000555555555225 in ?? ()
>>
>> On Thu, May 5, 2022 at 5:48 AM Matt Wette <matt.wette@gmail.com> wrote:
>>
>>> 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
>>> #1 0x00007ffff7bdd9da in GC_init_linux_data_start ()
>>> from /lib/x86_64-linux-gnu/libgc.so.1
>>> #2 0x00007ffff7bdef67 in GC_init () from
>> /lib/x86_64-linux-gnu/libgc.so.1
>>> #3 0x00007ffff7eda391 in scm_storage_prehistory ()
>>> at ../../guile-3.0.8-dist/libguile/gc.c:465
>>> #4 scm_i_init_guile (base=0x7fffffffde30)
>>> at ../../guile-3.0.8-dist/libguile/init.c:360
>>> #5 0x00007ffff7f41eff in scm_i_init_guile (base=0x7fffffffde30)
>>> at ../../guile-3.0.8-dist/libguile/init.c:357
>>> #6 scm_i_init_thread_for_guile (base=base@entry=0x7fffffffde30,
>>> dynamic_state=dynamic_state@entry=0x0)
>>> at ../../guile-3.0.8-dist/libguile/threads.c:570
>>> #7 0x00007ffff7f4231e in scm_i_init_thread_for_guile (dynamic_state=0x0,
>>> base=0x7fffffffde30) at
>> ../../guile-3.0.8-dist/libguile/threads.c:653
>>> #8 with_guile (base=0x7fffffffde30, data=0x7fffffffde60)
>>> at ../../guile-3.0.8-dist/libguile/threads.c:638
>>> #9 0x00007ffff7bdd80b in GC_call_with_stack_base ()
>>> from /lib/x86_64-linux-gnu/libgc.so.1
>>> #10 0x00007ffff7f3d3dc in scm_i_with_guile (dynamic_state=<optimized
>> out>,
>>> data=<optimized out>, func=<optimized out>)
>>> --Type <RET> for more, q to quit, c to continue without paging--
>>> at ../../guile-3.0.8-dist/libguile/threads.c:688
>>> #11 scm_with_guile (func=<optimized out>, data=<optimized out>)
>>> at ../../guile-3.0.8-dist/libguile/threads.c:694
>>> #12 0x00007ffff7eda2c9 in scm_boot_guile (argc=argc@entry=1,
>>> argv=argv@entry=0x7fffffffe018,
>>> main_func=main_func@entry=0x555555555320 <inner_main>,
>>> closure=closure@entry=0x0) at
>>> ../../guile-3.0.8-dist/libguile/init.c:295
>>> #13 0x00005555555551af in main (argc=1, argv=0x7fffffffe018)
>>> at ../../guile-3.0.8-dist/libguile/guile.c:94
>>> (gdb)
>>>
>>>
>>>
>>>
next prev parent reply other threads:[~2022-05-05 19:22 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 [this message]
2022-05-06 8:47 ` Andrew Burgess
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=f66f1b87-e006-52e2-ea02-e1640d681bcf@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@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).