From: Rob Browning <rlb@defaultvalue.org>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Thread+GC issues on ARM
Date: Fri, 10 Feb 2012 21:39:31 -0600 [thread overview]
Message-ID: <87mx8qghsc.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87fwfqqyhl.fsf@neil-laptop.ossau.uklinux.net> (Neil Jerram's message of "Sun, 08 Jan 2012 10:28:54 +0000")
Neil Jerram <neil@ossau.homelinux.net> writes:
> Rob Browning <rlb@defaultvalue.org> writes:
>> So do I understand correctly that in order for this to work, we'll first
>> need an updated libgc in Debian unstable?
>
> Yes.
Great. If we can get this and the s390 problem fixed, I'll be able to
see about removing 1.8 from Debian testing (which I'd love to do soon --
I'd really like to drop 1.8 from the upcoming release).
>> If so, I'll probably hold off on the guile patch for now.
>
> Sure. I'm happy that it's with me, for the moment, to propose something
> coherent to the libgc maintainer.
Could this also be related to the other current 2.0.5 arm(el|hf)
failures:
https://buildd.debian.org/status/package.php?p=guile-2.0&suite=sid
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10646
If it helps, I just tried debugging that problem on an armhf machine, and
test-with-guile-module fails like this:
Reading symbols from /home/rlb/guile/guile-2.0-2.0.3+1/test-suite/standalone/.libs/lt-test-with-guile-module...done.
(gdb) run
Starting program: /home/rlb/guile/guile-2.0-2.0.3+1/test-suite/standalone/.libs/lt-test-with-guile-module
[Thread debugging using libthread_db enabled]
[New Thread 0xb6afa470 (LWP 11969)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6afa470 (LWP 11969)]
0xb6eb512c in GC_malloc () from /usr/lib/libgc.so.1
(gdb) where
#0 0xb6eb512c in GC_malloc () from /usr/lib/libgc.so.1
#1 0xb6f78f80 in scm_cell (cdr=2721088, car=383) at ../libguile/inline.h:117
#2 guilify_self_2 (parent=0x2976f0) at threads.c:580
#3 0xb6f79962 in scm_i_init_thread_for_guile (base=0xb6af9dc4, parent=0x2976f0) at threads.c:821
#4 0xb6f7999c in with_guile_and_parent (base=0xb6af9dc4, data=<optimized out>) at threads.c:865
#5 0xb6eb24ea in GC_call_with_stack_base () from /usr/lib/libgc.so.1
#6 0xb6f79ad8 in scm_i_with_guile_and_parent (parent=<optimized out>, data=0x0, func=0x87dd <thread_inner_main>) at threads.c:915
#7 scm_with_guile (func=0x87dd <thread_inner_main>, data=<optimized out>) at threads.c:921
#8 0x0000879c in thread_main (unused=<optimized out>) at test-with-guile-module.c:50
#9 0xb6deaee8 in start_thread (arg=0xb6afa470) at pthread_create.c:306
#10 0xb6d929e8 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:116 from /lib/arm-linux-gnueabihf/libc.so.6
#11 0xb6d929e8 in ?? () at ../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:116 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2012-02-11 3:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 12:50 Thread+GC issues on ARM Neil Jerram
2012-01-07 1:39 ` Andy Wingo
2012-01-07 3:32 ` Rob Browning
2012-01-07 12:01 ` Neil Jerram
2012-01-07 12:35 ` Neil Jerram
2012-01-07 17:52 ` Rob Browning
2012-01-08 10:28 ` Neil Jerram
2012-02-11 3:39 ` Rob Browning [this message]
2012-02-11 9:58 ` Neil Jerram
2012-02-11 13:10 ` Neil Jerram
2012-02-11 17:39 ` Rob Browning
2012-02-13 22:22 ` Neil Jerram
2012-02-11 17:38 ` Rob Browning
2013-01-16 10:28 ` Andy Wingo
2012-01-07 16:48 ` Rob Browning
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=87mx8qghsc.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.homelinux.net \
--cc=wingo@pobox.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).