unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Welsh Duggan <mwd@cert.org>
Cc: 23522@debbugs.gnu.org
Subject: bug#23522: 25.0.93; SEGFAULT when displaying HELLO
Date: Thu, 12 May 2016 22:16:48 +0300	[thread overview]
Message-ID: <83lh3f9jdr.fsf@gnu.org> (raw)
In-Reply-To: <tntvb2jtckl.fsf@watermonitor.yellow.cert.org> (message from Michael Welsh Duggan on Thu, 12 May 2016 13:23:38 -0400)

> From: Michael Welsh Duggan <mwd@cert.org>
> Date: Thu, 12 May 2016 13:23:38 -0400
> Cc: 23522@debbugs.gnu.org
> 
> > HELLO crash plus "old" RHEL makes me think of
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=844776
> >
> > Could you be getting libotf from openmpi instead?
> 
> Unlikely.  This system does not have openmpi installed.  No openmpi
> packages, and no files with openmpi in the filename found by locate.
> 
> Also, the error is a segfault, rather than a "symbol lookup error".

Please rebuild without optimizations, with --enable-checking, and with
"-g3" in the compiler switches, reproduce the problem, and post the
backtrace you get then.

Thanks.





  reply	other threads:[~2016-05-12 19:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 13:05 bug#23522: 25.0.93; SEGFAULT when displaying HELLO Michael Welsh Duggan
2016-05-12 16:40 ` Glenn Morris
2016-05-12 17:23   ` Michael Welsh Duggan
2016-05-12 19:16     ` Eli Zaretskii [this message]
2016-05-12 19:58       ` Michael Welsh Duggan
2016-05-12 20:28         ` Eli Zaretskii
2016-05-12 20:49           ` Michael Welsh Duggan
2016-05-13  7:46             ` Eli Zaretskii
2016-05-13 14:52               ` Michael Welsh Duggan
2016-05-13 15:14                 ` Eli Zaretskii
2016-05-13 18:06                   ` Michael Welsh Duggan
2016-05-13 18:53                     ` Eli Zaretskii
2016-05-13 19:17                       ` Michael Welsh Duggan
2019-11-08  4:22                         ` Stefan Kangas
2019-11-08 10:30                           ` Eli Zaretskii
2019-11-08 15:16                             ` Michael Welsh Duggan
2019-11-09  7:45                               ` Stefan Kangas

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lh3f9jdr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23522@debbugs.gnu.org \
    --cc=mwd@cert.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).