From: Douglas Mencken <dougmencken@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org, neil@ossau.uklinux.net
Subject: Re: build errors: 9172 Broken pipe and 9173 Segmentation fault
Date: Sat, 16 Apr 2011 13:19:55 +0200 [thread overview]
Message-ID: <BANLkTik8yKovzgB=EXytqxL3cggL4-cbNA@mail.gmail.com> (raw)
In-Reply-To: <m3pqp6uyo5.fsf@unquote.localdomain>
Hi again!
Yes, you fixed infinite loop issue, thank you. But guile 2.0 (now it
is guile-v2.0.0-199-g0fbdbe6 -- currently the latest one from
stable-2.0 branch) is still un-buildable on my side.
I summarized what I did here (section "Example: debugging guile build
error"): http://manulix.wikidot.com/debug-howto
Duping the output of 'thread apply all bt' also here:
Thread 1 (Thread 18507):
#0 0x48470744 in raise () from /lib/libc.so.0
#1 0x4846aef0 in abort () from /lib/libc.so.0
#2 0x480ebc64 in scm_throw (key=0x0, args=0x10317ff0) at throw.c:102
#3 0x480e0f44 in scm_decoding_error (subr=<value optimized out>,
err=38, message=<value optimized out>, port=<value optimized out>) at
strings.c:1438
#4 0x480e1190 in scm_from_stringn (str=0x48128754 ������, len=<value
optimized out>, encoding=<value optimized out>, handler=<value
optimized out>) at strings.c:1494
#5 0x480e11e8 in scm_from_locale_stringn (str=0x48128754 ������,
len=<value optimized out>) at strings.c:1535
#6 0x480e7304 in scm_from_locale_symboln (sym=<value optimized out>,
len=<value optimized out>) at symbols.c:444
#7 0x480e7328 in scm_from_locale_symbol (sym=<value optimized out>)
at symbols.c:438
#8 0x48050410 in scm_init_array_handle () at array-handle.c:138
#9 0x480894c0 in scm_i_init_guile (base=<value optimized out>) at init.c:399
#10 0x480e8e5c in scm_i_init_thread_for_guile (base=0xbfcd9fc8,
parent=0x0) at threads.c:777
#11 scm_i_init_thread_for_guile (base=0xbfcd9fc8, parent=0x0) at threads.c:756
#12 0x480e8eb0 in with_guile_and_parent (base=0xbfcd9fc8, data=<value
optimized out>) at threads.c:849
#13 0x4817f718 in GC_call_with_stack_base (fn=<value optimized out>,
arg=<value optimized out>) at misc.c:1480
#14 0x480e9074 in scm_i_with_guile_and_parent (func=<value optimized
out>, data=<value optimized out>) at threads.c:899
#15 scm_with_guile (func=<value optimized out>, data=<value optimized
out>) at threads.c:905
#16 0x48089438 in scm_boot_guile (argc=<value optimized out>,
argv=<value optimized out>, main_func=<value optimized out>,
closure=<value optimized out>) at init.c:319
#17 0x100006c4 in main (argc=<value optimized out>, argv=<value
optimized out>) at guile.c:70
next prev parent reply other threads:[~2011-04-16 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 1:05 build errors: 9172 Broken pipe and 9173 Segmentation fault Douglas Mencken
2011-03-24 1:45 ` Neil Jerram
[not found] ` <AANLkTindvcPaJ4qYr7OCvWbitFCzb2oALNO1ya6x0_Y4@mail.gmail.com>
2011-03-29 17:07 ` Douglas Mencken
2011-04-01 9:08 ` Andy Wingo
2011-04-16 11:19 ` Douglas Mencken [this message]
2011-04-16 16:01 ` Andy Wingo
2011-04-17 2:34 ` Mark H Weaver
2011-04-18 21:16 ` Ludovic Courtès
2011-04-18 23:45 ` Mark H Weaver
2011-04-21 10:28 ` Andy Wingo
2011-04-17 2:38 ` Mark H Weaver
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='BANLkTik8yKovzgB=EXytqxL3cggL4-cbNA@mail.gmail.com' \
--to=dougmencken@gmail.com \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.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).