From: Greg Troxel <gdt@ir.bbn.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: boehm-gc troubles with 2.0.10 on NetBSD/i386
Date: Fri, 11 Apr 2014 15:39:55 -0400 [thread overview]
Message-ID: <rmimwfr7j04.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87ioqffztd.fsf@yeeloong.lan> (Mark H. Weaver's message of "Fri, 11 Apr 2014 15:09:34 -0400")
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
Mark H Weaver <mhw@netris.org> writes:
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to LWP 1]
>> 0xbba868ae in GC_find_limit_with_bound () from /usr/pkg/lib/libgc.so.1
>> (gdb) bt
>> #0 0xbba868ae in GC_find_limit_with_bound () from /usr/pkg/lib/libgc.so.1
>> #1 0xbba8696e in GC_find_limit () from /usr/pkg/lib/libgc.so.1
>> #2 0xbba8699d in GC_init_netbsd_elf () from /usr/pkg/lib/libgc.so.1
>> #3 0xbba85b3f in GC_init () from /usr/pkg/lib/libgc.so.1
>> #4 0xbbaf9748 in scm_storage_prehistory () from .libs/libguile-2.0.so.29
>> #5 0xbbb0abaf in scm_i_init_guile () from .libs/libguile-2.0.so.29
>> #6 0xbbb6712c in scm_i_init_thread_for_guile () from .libs/libguile-2.0.so.29
>> #7 0xbbb67347 in with_guile_and_parent () from .libs/libguile-2.0.so.29
>> #8 0xbba85767 in GC_call_with_stack_base () from /usr/pkg/lib/libgc.so.1
>> #9 0xbbb67529 in scm_with_guile () from .libs/libguile-2.0.so.29
>> #10 0xbbb0ab67 in scm_boot_guile () from .libs/libguile-2.0.so.29
>> #11 0x08048ce9 in main ()
>
> My guess is that this SIGSEGV is probably intentional, perhaps the
> method used by GC on NetBSD to determine the bounds of the stack or some
> other data area. I would try continuing and seeing what happens next.
> GC may also use some other signals for its own purposes.
continuing leads to the program exiting. I should build libgc with
debugging...
>> LICENSE= gnu-gpl-v3
>
> I think this license field is incorrect. Guile's license is the GNU
> _Lesser_ General Public License v3-or-later.
Is everything that is installed under LGPL, even readline?
(But even if so, that should say "gnu-gpl-v3 AND gnu-lgpl-v3".)
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2014-04-11 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 13:14 boehm-gc troubles with 2.0.10 on NetBSD/i386 Greg Troxel
2014-04-11 17:21 ` Mark H Weaver
2014-04-11 18:14 ` Greg Troxel
2014-04-11 19:09 ` Mark H Weaver
2014-04-11 19:39 ` Greg Troxel [this message]
2014-04-11 21:54 ` Mark H Weaver
2014-04-22 13:01 ` boehm-gc troubles with 2.0.11 " Greg Troxel
2014-04-22 14:39 ` Taylan Ulrich Bayirli/Kammer
2014-04-22 16:14 ` Mark H Weaver
2014-09-20 6:16 ` In-Ho Yi
2014-09-20 23:25 ` Mark H Weaver
2014-04-12 10:16 ` boehm-gc troubles with 2.0.10 " Ludovic Courtès
2014-04-12 17:06 ` Mark H Weaver
2014-04-12 23:56 ` Greg Troxel
2014-04-12 10:15 ` 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=rmimwfr7j04.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).