unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Scott N. Walck" <walck@lvc.edu>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: set-current-module in .guile ?
Date: Mon, 7 Apr 2008 11:07:35 -0400	[thread overview]
Message-ID: <18426.14519.36960.278300@entangle.lvc.edu> (raw)
In-Reply-To: <87fxtxrdhw.fsf@gnu.org>

Hi,

Thanks for the "ulimit -c unlimited" command.

Here is the backtrace from gdb.

[walck@entangle:~]$ ulimit -c unlimited
[walck@entangle:~]$ guile
guile> (load "/usr/local/src/guile-scmutils/src/load.scm")
guile> (module-use! (current-module) generic-environment)
#f
guile> +
#<procedure g:+ args>
guile> (+ (vector 5 6) (vector 7 8))
Segmentation fault (core dumped)
[walck@entangle:~]$ ls core*
core.18853
[walck@entangle:~]$ gdb `which guile` core.18853
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x915000
Core was generated by `guile'.
Program terminated with signal 11, Segmentation fault.

warning: svr4_current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/local/lib/libguile.so.17...done.
Loaded symbols for /usr/local/lib/libguile.so.17
Reading symbols from /usr/lib/sse2/libgmp.so.3...done.
Loaded symbols for /usr/lib/sse2/libgmp.so.3
Reading symbols from /lib/libcrypt.so.1...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/local/lib/libltdl.so.3...done.
Loaded symbols for /usr/local/lib/libltdl.so.3
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/local/lib/libguilereadline-v-17.so.17...done.
Loaded symbols for /usr/local/lib/libguilereadline-v-17.so.17
Reading symbols from /usr/lib/libreadline.so.5...done.
Loaded symbols for /usr/lib/libreadline.so.5
Reading symbols from /usr/lib/libncurses.so.5...done.
Loaded symbols for /usr/lib/libncurses.so.5
Reading symbols from /usr/local/lib/libguile-srfi-srfi-1-v-3.so.3...done.
Loaded symbols for /usr/local/lib/libguile-srfi-srfi-1-v-3.so.3
#0  0x00168d0c in scm_hash_fn_get_handle (table=0xb7f01560, obj=0xb7ef7190, 
    hash_fn=0x167b40 <scm_ihashq>, assoc_fn=0x1393d0 <scm_sloppy_assq>, 
    closure=0x0) at hashtab.c:415
415	{
(gdb) bt
#0  0x00168d0c in scm_hash_fn_get_handle (table=0xb7f01560, obj=0xb7ef7190, 
    hash_fn=0x167b40 <scm_ihashq>, assoc_fn=0x1393d0 <scm_sloppy_assq>, 
    closure=0x0) at hashtab.c:415
#1  0x00169d59 in scm_hash_fn_ref (table=0xb7f01560, obj=0xb7ef7190, 
    dflt=0x4, hash_fn=0x167b40 <scm_ihashq>, 
    assoc_fn=0x1393d0 <scm_sloppy_assq>, closure=0x0) at hashtab.c:500
#2  0x00169eff in scm_hashq_ref (table=0xb7f01560, key=0xb7ef7190, dflt=0x204)
    at hashtab.c:613
#3  0x0016fa78 in module_variable (module=0xb7f01590, sym=0xb7ef7190)
    at modules.c:289
#4  0x0016fae5 in module_variable (module=Variable "module" is not available.
) at modules.c:307
#5  0x0016fae5 in module_variable (module=Variable "module" is not available.
) at modules.c:307
#6  0x0016fae5 in module_variable (module=Variable "module" is not available.
) at modules.c:307

Thanks,

Scott



Ludovic Courtès writes:
 > Hi,
 > 
 > "Walck, Scott" <walck@lvc.edu> writes:
 > 
 > > I don't think it's the + function.  I get a segfault just by typing
 > > (exit).  I don't get a core file, though, in either case.  Why is
 > > that?
 > 
 > You do get a core file since it says "core dumped".  Maybe it's named
 > `core.123' or something like that instead of just `core'.  Otherwise,
 > type "ulimit -c unlimited" and try again.
 > 
 > Thanks,
 > Ludovic.
 > 
 > 
 > 
 > 






  reply	other threads:[~2008-04-07 15:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 17:24 set-current-module in .guile ? Scott N. Walck
2008-04-05 21:00 ` Jon Wilson
2008-04-06  0:01   ` Walck, Scott
2008-04-06 14:58     ` Ludovic Courtès
2008-04-07  1:27       ` Walck, Scott
2008-04-07  7:16         ` Ludovic Courtès
2008-04-07 11:27           ` Walck, Scott
2008-04-07 13:38             ` Ludovic Courtès
2008-04-07 15:07               ` Scott N. Walck [this message]
2008-04-08 13:40                 ` Ludovic Courtès
2008-04-08 15:41                   ` Scott N. Walck
2008-04-09 15:05                 ` Ludovic Courtès
2008-04-09 15:24                   ` Walck, Scott
2008-04-09 20:16 ` Neil Jerram

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=18426.14519.36960.278300@entangle.lvc.edu \
    --to=walck@lvc.edu \
    --cc=guile-user@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).