unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 33174@debbugs.gnu.org
Subject: bug#33174: 27.0.50; Dump fails on GNU/Linux ppc64le
Date: Sun, 28 Oct 2018 01:05:09 -0700	[thread overview]
Message-ID: <b8d37c56-62e9-e6b7-85df-2847a980a495@cs.ucla.edu> (raw)
In-Reply-To: <ca2934d1-28ad-2042-e2c7-8d85c98e3795@cs.ucla.edu>

I built and ran Emacs master on two CentOS 7 ppc64le platforms with no trouble. 
So the problem is not GNU/Linux ppc64le per se; it's something more specific to 
your platform. Here are some characteristics of my builds:

Emacs master branch commit 3dd16a89bf410d77e9ddc41cbfbbd4b343928d6d

./configure --with-x-toolkit=no --with-xpm=no --with-jpeg=no --with-png=no 
--with-gif=no --with-tiff=no

Both machines were CentOS 7. On both of them, 
/proc/sys/kernel/randomize_va_space is 2, just as in your Debian machine.

uname -rvmpi reported the following (respectively):
3.10.0-693.11.6.el7.ppc64le #1 SMP Thu Jan 4 18:15:24 GMT 2018 ppc64le ppc64le 
ppc64le
4.14.0-49.13.1.el7a.ppc64le #1 SMP Wed Sep 26 21:58:41 GMT 2018 ppc64le ppc64le 
ppc64le

gcc --version reported the following (respectively):
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28)

On the machine running 4.14.0, there was no setfattr or getfattr command; 
however, ./temacs personality (0xffffffff) returned 0x40000 (i.e., 
ADDR_NO_RANDOMIZE) and so ./temacs did not reexec itself. I don't know why it 
returned 0x40000; even little programs that only call personality (0xffffffff) 
return 0x40000 on this platform.





  reply	other threads:[~2018-10-28  8:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 10:35 bug#33174: 27.0.50; Dump fails on GNU/Linux ppc64le Thomas Fitzsimmons
2018-10-27 13:16 ` Thomas Fitzsimmons
2018-10-27 20:26   ` Paul Eggert
2018-10-28  8:05     ` Paul Eggert [this message]
2018-10-28 12:56       ` Thomas Fitzsimmons
2018-10-28 19:22         ` Paul Eggert
2018-10-30  1:28           ` Thomas Fitzsimmons
2018-10-30  2:16             ` Paul Eggert
2018-10-29  1:47     ` Thomas Fitzsimmons
2018-10-29  7:22       ` Paul Eggert
2018-10-30  2:44         ` Thomas Fitzsimmons
2018-10-30  5:58           ` Paul Eggert
2018-10-30  9:30             ` Thomas Fitzsimmons
2018-11-12  6:39               ` Paul Eggert
2018-11-12 17:24                 ` Andy Moreton
2018-11-13  2:29                 ` Thomas Fitzsimmons
2018-11-13 14:42                   ` Paul Eggert
2018-11-19  3:14                     ` Thomas Fitzsimmons

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=b8d37c56-62e9-e6b7-85df-2847a980a495@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=33174@debbugs.gnu.org \
    --cc=fitzsim@fitzsim.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).