unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Peter TB Brett <peter@peter-b.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Help needed debugging segfault with Guile 1.8.7
Date: Thu, 11 Nov 2010 08:33:48 +0000	[thread overview]
Message-ID: <87aalg9s43.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3wrol5oxx.fsf@harrington.peter-b.co.uk> (Peter TB Brett's message of "Wed, 10 Nov 2010 12:43:38 +0000")

Peter TB Brett <peter@peter-b.co.uk> writes:

> I'd really appreciate any suggestions that anyone might be able to give
> me on figuring out how I've managed to break things.  At the moment, I'm
> at a complete loss.

I'm afraid I only have two general ideas.

1. You can use gdb_print and gdb_output to see the Scheme values of SCM
variables.  For example, to see the value of `l', in the top frame of
your backtrace:

(gdb) call gdb_print(l)
(gdb) p gdb_output

2. You can try modifying your script in small ways to see if the problem
disappears.  If it does, that may give a clue about what the problem is.

Regards,
        Neil



  parent reply	other threads:[~2010-11-11  8:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 12:43 Help needed debugging segfault with Guile 1.8.7 Peter TB Brett
2010-11-10 21:35 ` Peter TB Brett
2010-11-11 10:52   ` Peter Brett
2010-11-11 12:37     ` Thien-Thi Nguyen
2010-11-11 14:22       ` Peter Brett
2010-11-28 11:38         ` Neil Jerram
2010-11-28 17:21           ` Linas Vepstas
2010-11-30 19:56             ` Peter TB Brett
2010-12-01 19:48               ` Andy Wingo
2010-11-30 19:43           ` Peter TB Brett
2010-12-01 13:46             ` Ludovic Courtès
2010-12-03  7:52               ` Peter TB Brett
2010-11-11  8:22 ` rixed
2010-11-11  8:33 ` Neil Jerram [this message]
2010-11-11 13:30 ` 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=87aalg9s43.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-user@gnu.org \
    --cc=peter@peter-b.co.uk \
    /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).