unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-devel@gnu.org
Subject: Re: boehm-gc troubles with 2.0.10 on NetBSD/i386
Date: Fri, 11 Apr 2014 15:09:34 -0400	[thread overview]
Message-ID: <87ioqffztd.fsf@yeeloong.lan> (raw)
In-Reply-To: <rmi4n1z91io.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "Fri, 11 Apr 2014 14:14:39 -0400")

Greg Troxel <gdt@ir.bbn.com> writes:

> After fixing the --disable-threads and updating to 2.0.11, I get the
> following.  I'll ask pkgsrc/netbsd people about libgc, since that seems
> to be the issue.
>
> /usr/pkgsrc/wip/guile2/work/guile-2.0.11/libguile > LD_LIBRARY_PATH=.libs gdb .libs/guile 
> GNU gdb (GDB) 7.3.1
> Copyright (C) 2011 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 "i486--netbsdelf".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from
> /u0/n0/gdt/NetBSD-current/pkgsrc/wip/guile2/work/guile-2.0.11/libguile/.libs/guile...(no
> debugging symbols found)...done.
> (gdb) run
> Starting program: /u0/n0/gdt/NetBSD-current/pkgsrc/wip/guile2/work/guile-2.0.11/libguile/.libs/guile 
>
> 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.

> I realize this packaging control file is a foreign language, but here's how it looks:
>
>   # $NetBSD$
>   #
>
>   DISTNAME=	guile-2.0.11
>   CATEGORIES=	lang
>   MASTER_SITES=	ftp://ftp.gnu.org/gnu/guile/
>
>   MAINTAINER=	root@zta.lk
>   HOMEPAGE=	ftp://ftp.gnu.org/gnu/guile/
>   COMMENT=	Official extension language for the GNU operating system
>   LICENSE=	gnu-gpl-v3

I think this license field is incorrect.  Guile's license is the GNU
_Lesser_ General Public License v3-or-later.

     Mark



  reply	other threads:[~2014-04-11 19:09 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 [this message]
2014-04-11 19:39       ` Greg Troxel
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=87ioqffztd.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=gdt@ir.bbn.com \
    --cc=guile-devel@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).