From: tantalum <theseph@gmx.de>
To: bug-guile@gnu.org
Subject: Re: guile 1.8.5 compile segfault
Date: Tue, 23 Sep 2008 20:35:33 +0200 [thread overview]
Message-ID: <48D936F5.2070409@gmx.de> (raw)
x86_64 is the same as amd64, just a vendor neutral name.
(http://en.wikipedia.org/wiki/X86-64)
i use gcc 4.3.2-1
2008/9/22 Neil Jerram <neiljerram@googlemail.com>:
> Once you're in GDB, type bt to get the stack, and if you can a few
> prints to identify the immediate cause of the fault
im not sure what you mean by prints. the frame command in gdb?
i managed to get a core dump file. heres a backtrace and some "frame x"
calling:
http://pastebin.com/m3c55053b
> could you work around this by using Guile on a less troublesome platform?
that is a good idea. i will try to get a setup on another machine i can
ssh to.
to compile guile 1.8.5 (release or snapshot-0923) on this i386 other
machine, i need to apply this patch, found via google:
http://pastebin.com/m6226ece1
otherwise it stops leaving its long message, end of which is:
http://pastebin.com/m102992ca
it looks like this error happens at a very similar position as the
segfault error.
im not too sure if the patch does a good thing, as i ran into strange
problems with guile-gnome.
next reply other threads:[~2008-09-23 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 18:35 tantalum [this message]
2008-10-13 22:38 ` guile 1.8.5 compile segfault Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2008-09-22 17:25 tantalum
2008-09-22 19:29 ` Neil Jerram
2008-09-21 13:01 tantalum
2008-09-21 21:27 ` Neil Jerram
2008-09-20 13:31 tantalum
2008-09-21 9:43 ` Neil Jerram
2008-09-19 16:14 tantalum
2008-09-19 22:48 ` 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=48D936F5.2070409@gmx.de \
--to=theseph@gmx.de \
--cc=bug-guile@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).