unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: Aidan Gauland <aidalgol@no8wireless.co.nz>,
	Mike Gran <spk121@yahoo.com>,
	 "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: C module problem
Date: Mon, 28 Feb 2011 12:30:31 -0500	[thread overview]
Message-ID: <20110228173032.SYRSD.231534.root@cdptpa-web09-z02> (raw)
In-Reply-To: <440851.45861.qm@web37908.mail.mud.yahoo.com>


---- Mike Gran <spk121@yahoo.com> wrote: 

> On Linux (the kernel), to see if this is the case (and I'm going
> from memory here, so forgive me if this isn't perfect) you can
> run guile as
> 
> "LD_DEBUG=all LD_DEBUG_OUTPUT=tmp.txt guile"
> 
> and then try to load your extension.
> 
> Then after your run, it should have made a handful of tmp.txt files, one
> per thread.  Search through these files for strings like "error" or "fatal"
> with reference to your binding.  It may be that you've misspelled a function
> name or are trying to link to a function that doesn't exist.

It is also instructive to run the command under strace -efile.  You get a clear idea of what file guile *is* trying to open and *where*.

I've solved more "can't open the file" type problems with strace than I can remember.  A wonderful tool.

-Dale




  parent reply	other threads:[~2011-02-28 17:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 14:54 C module problem Mike Gran
2011-02-28 15:35 ` gustav
2011-02-28 17:30 ` dsmich [this message]
2011-02-28 18:24   ` Aidan Gauland
2011-02-28 20:43     ` Aidan Gauland
  -- strict thread matches above, loose matches on Subject: below --
2011-02-28  9:40 nalaginrut
2011-02-28 10:16 ` rm
2011-02-28  8:13 Aidan Gauland
2011-02-28  8:54 ` nalaginrut
2011-02-28  9:32   ` Aidan Gauland
2011-02-28 21:37 ` Andy Wingo
2011-02-28 23:23   ` Aidan Gauland

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=20110228173032.SYRSD.231534.root@cdptpa-web09-z02 \
    --to=dsmich@roadrunner.com \
    --cc=aidalgol@no8wireless.co.nz \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.com \
    /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).