From: Andy Wingo <wingo@pobox.com>
To: "Stewart\, Adam James" <ajstewart@anl.gov>
Cc: 23911@debbugs.gnu.org
Subject: bug#23911: Cat broken pipe segmentation fault when building Guile
Date: Mon, 11 Jul 2016 21:35:54 +0200 [thread overview]
Message-ID: <874m7w3r39.fsf@pobox.com> (raw)
In-Reply-To: <9F5501637440B04B9DE4C86279C60B6E4A575001@PAYTON.anl.gov> (Adam James Stewart's message of "Mon, 11 Jul 2016 16:36:10 +0000")
Hi,
Please keep the debbugs link in Cc. Thanks :)
On Mon 11 Jul 2016 18:36, "Stewart, Adam James" <ajstewart@anl.gov> writes:
> I tried your suggestion for getting the backtrace but I'm not sure if I did it correctly:
>
> $ gdb libguile/.libs/guile libguile/core-lt-guile-11-7459-3024-47528-1468254675
> Reading symbols from /scratch/ajstewart/spack-stage/spack-stage-6loD5i/guile-2.0.11.224-5b7b5/libguile/.libs/guile...done.
> (gdb) bt
> No stack.
> (gdb)
Weird. I guess this meant that nothing else had debug symbols, only
Guile.
How about running:
GUILE_AUTO_COMPILE=0 meta/guile
What does that print out?
Andy
next prev parent reply other threads:[~2016-07-11 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:03 bug#23911: Cat broken pipe segmentation fault when building Guile Stewart, Adam James
2016-07-10 12:42 ` Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A574FC1@PAYTON.anl.gov>
2016-07-11 15:55 ` Andy Wingo
[not found] ` <9F5501637440B04B9DE4C86279C60B6E4A575001@PAYTON.anl.gov>
2016-07-11 19:35 ` Andy Wingo [this message]
2016-07-13 17:00 ` Stewart, Adam James
2016-07-13 20:45 ` Stewart, Adam James
2016-07-14 10:11 ` Andy Wingo
2017-03-01 8:12 ` Andy Wingo
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=874m7w3r39.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=23911@debbugs.gnu.org \
--cc=ajstewart@anl.gov \
/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).