From: "Stewart, Adam James" <ajstewart@anl.gov>
To: Andy Wingo <wingo@pobox.com>
Cc: "23911@debbugs.gnu.org" <23911@debbugs.gnu.org>
Subject: bug#23911: Cat broken pipe segmentation fault when building Guile
Date: Wed, 13 Jul 2016 17:00:32 +0000 [thread overview]
Message-ID: <9F5501637440B04B9DE4C86279C60B6E4A5753B9@PAYTON.anl.gov> (raw)
In-Reply-To: <9F5501637440B04B9DE4C86279C60B6E4A575001@PAYTON.anl.gov>
Andy,
$ GUILE_AUTO_COMPILE=0 meta/guile
Segmentation fault (core dumped)
$ gdb libguile/.libs/guile libguile/core-lt-guile-11-7459-3024-47618-1468428920
Reading symbols from /scratch/ajstewart/spack-stage/spack-stage-c8z012/guile-2.0.11/libguile/.libs/guile...done.
(gdb) bt
No stack.
(gdb) quit
$ gdb libguile/.libs/guile core-lt-guile-11-7459-3024-47708-1468428949
Reading symbols from /scratch/ajstewart/spack-stage/spack-stage-c8z012/guile-2.0.11/libguile/.libs/guile...done.
(gdb) bt
No stack.
(gdb)
Those were the only two *core* files in my build root directory.
I'm currently building all of Guile's dependencies by hand, so there is always a chance there's an error in one of those libraries. I'm going to try building with as many of the system libraries as I can. Maybe I'll discover a bug in one of my installs.
Adam J. Stewart
Assistant Systems Administrator
Laboratory Computing Resource Center
Computing, Environment and Life Sciences
Argonne National Laboratory
________________________________________
From: Stewart, Adam James
Sent: Monday, July 11, 2016 11:36 AM
To: Andy Wingo
Subject: RE: bug#23911: Cat broken pipe segmentation fault when building Guile
Andy,
I tried unsetting LANG and LC_ALL but that didn't help. Nor did setting them to C instead of en_US.UTF-8. If you have any more locale suggestions I can try them.
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)
I've used gdb before, but I don't normally debug core dumps, so you may have to give me some pointers.
Adam J. Stewart
Assistant Systems Administrator
Laboratory Computing Resource Center
Computing, Environment and Life Sciences
Argonne National Laboratory
________________________________________
From: Andy Wingo [wingo@pobox.com]
Sent: Monday, July 11, 2016 10:55 AM
To: Stewart, Adam James
Cc: 23911@debbugs.gnu.org
Subject: Re: bug#23911: Cat broken pipe segmentation fault when building Guile
On Mon 11 Jul 2016 15:05, "Stewart, Adam James" <ajstewart@anl.gov> writes:
> I just tried the prerelease tarball you suggested but am getting the
> same problem. My config.log, build output, and build environment
> variables are attached.
Thanks; all looked fine except that `environ_locale_charset' thing;
dunno.
Would you mind getting a backtrace from the core to see what happened?
It says "core dumped" so assuming you can find the core then you do "gdb
libguile/.libs/guile libguile/core" (assuming the core file is dumped in
the libguile directory), then "bt".
Cheers,
Andy
next prev parent reply other threads:[~2016-07-13 17:00 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
2016-07-13 17:00 ` Stewart, Adam James [this message]
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=9F5501637440B04B9DE4C86279C60B6E4A5753B9@PAYTON.anl.gov \
--to=ajstewart@anl.gov \
--cc=23911@debbugs.gnu.org \
--cc=wingo@pobox.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).