From: Roland Orre <roland.orre@neurologic.se>
To: guile-user@gnu.org
Subject: Debugging hints wanted
Date: Mon, 30 Jun 2008 18:56:22 +0200 [thread overview]
Message-ID: <1214844983.6032.96.camel@localhost.localdomain> (raw)
In-Reply-To: <20080204214003.GB2646@stratocaster.home>
I need hints on how to find occasional segmentation faults
and missed GC references. This relates to 64 bit machines.
Background:
When I started using 64 bit machines a few years ago most of
guile fine after I converted my modules to 64 bit code.
Apart from changes in my own C-code the only thing I changed
in guile was size of uvect,ivect in unif.c cells as they
by default become 64 bit long instead of 32 bit. My 64 bits
are dual-CPU/core though so it may be related to that
(still using guile 1.7) but I don't have any problem on
dual CPU 32 bits systems.
My modules have worked perfectly fine on 32 bit machines but
on 64 bits I occasionally get something like
#<freed cell 0x2...; GC missed a reference> if I run that
code fast, which indicates a threading problem (I do not use
threads in this case, but seems like guile does). This does
not occur if I run guile through gdb. This happens not too often
but it seems to be related to string->symbol symbol->string.
My bigger problem though is frequently occurring
segmentation faults or otherwise corrupt pointers.
If I then run the code in gdb I can get
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2ae316e4f070 (LWP 6699)]
0x00002ae314b9d091 in scm_gc_mark_dependencies (p=0x97c) at
gc-mark.c:441
441 if (SCM_GC_MARK_P (ptr))
Current language: auto; currently c
Grateful for any hints to trace these kinds of problems.
Roland Orre
next prev parent reply other threads:[~2008-06-30 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 19:19 guile-pg - debian David Pirotte
2008-02-04 21:40 ` Eric Cooper
2008-06-30 16:56 ` Roland Orre [this message]
2008-06-30 19:42 ` Debugging hints wanted Ludovic Courtès
2008-07-01 10:14 ` Roland Orre
2008-07-01 12:27 ` Ludovic Courtès
2008-07-01 14:24 ` Roland Orre
2008-07-01 15:00 ` Ludovic Courtès
2008-02-05 14:26 ` guile-pg - debian Greg Troxel
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=1214844983.6032.96.camel@localhost.localdomain \
--to=roland.orre@neurologic.se \
--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).