From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 10655@debbugs.gnu.org
Subject: bug#10655: [2.0.3+] ‘queue_after_gc_hook’ called during thread startup leads to SIGSEGV
Date: Mon, 30 Jan 2012 16:33:42 +0100 [thread overview]
Message-ID: <87mx95w6g9.fsf@pobox.com> (raw)
In-Reply-To: <87y5spxlcg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 30 Jan 2012 16:26:39 +0100")
On Mon 30 Jan 2012 16:26, ludo@gnu.org (Ludovic Courtès) writes:
> #0 queue_after_gc_hook (hook_data=<value optimized out>, fn_data=<value optimized out>,
> data=<value optimized out>) at gc.c:737
> #1 0x00007f236ea0518c in scm_c_hook_run (hook=0x7f236ed00a10, data=0x0) at hooks.c:103
> #2 0x00007f236e729951 in GC_notify_full_gc (stop_func=0x7f236e728e00 <GC_never_stop_func>)
> at alloc.c:334
> #3 GC_try_to_collect_inner (stop_func=0x7f236e728e00 <GC_never_stop_func>) at alloc.c:429
> #4 GC_try_to_collect_inner (stop_func=0x7f236e728e00 <GC_never_stop_func>) at alloc.c:410
> #5 0x00007f236e72a65e in GC_collect_or_expand (needed_blocks=1, ignore_off_page=0,
> retry=<value optimized out>) at alloc.c:1215
> #6 0x00007f236e72a7c6 in GC_allocobj (gran=42, kind=1) at alloc.c:1302
> #7 0x00007f236e72f61a in GC_generic_malloc_inner (lb=664, k=1) at malloc.c:121
> #8 0x00007f236e739aff in GC_new_thread (id=139790027667200) at pthread_support.c:478
> #9 0x00007f236e739fb7 in GC_register_my_thread_inner (sb=0x7f2366f12ed0,
> my_pthread=<value optimized out>) at pthread_support.c:1358
> #10 0x00007f236e73a167 in GC_start_rtn_prepare_thread (pstart=0x7f2366f12eb0,
> pstart_arg=0x7f2366f12eb8, sb=0x7f2366f12ed0, arg=0x2aa1fc0) at pthread_support.c:1449
> #11 0x00007f236e739993 in GC_inner_start_routine (sb=<value optimized out>,
> arg=<value optimized out>) at pthread_start.c:50
> #12 0x00007f236e7348d5 in GC_call_with_stack_base (fn=<value optimized out>,
> arg=<value optimized out>) at misc.c:1535
> #13 0x00007f236e504cec in start_thread ()
> from /nix/store/vxycd107wjbhcj720hzkw2px7s7kr724-glibc-2.12.2/lib/libpthread.so.0
> #14 0x00007f236d0111ed in clone ()
> from /nix/store/vxycd107wjbhcj720hzkw2px7s7kr724-glibc-2.12.2/lib/libc.so.6
>
> The problems seems to be that the after-gc-hook runs while the thread is
> being created and not yet a full-blown Guile thread.
Interesting. I'll see what I can do.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-30 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 15:26 bug#10655: [2.0.3+] ‘queue_after_gc_hook’ called during thread startup leads to SIGSEGV Ludovic Courtès
2012-01-30 15:33 ` Andy Wingo [this message]
2012-01-30 15:41 ` Ludovic Courtès
2012-01-30 19:42 ` Ludovic Courtès
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=87mx95w6g9.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10655@debbugs.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).