From: jhd <jan.h.d@swipnet.se>
Cc: yamaoka@jpl.org, yamato@redhat.com, emacs-devel@gnu.org
Subject: Re: New dumping problem...
Date: Sat, 2 Jul 2005 09:46:37 +0200 [thread overview]
Message-ID: <B4205B9F-7506-4E30-BF32-7FF49F4D1697@swipnet.se> (raw)
In-Reply-To: <E1DoUFu-0002ER-Sz@fencepost.gnu.org>
> FWIW, Fedora core 2 works OK with this change.
>
> Does that mean we can delete the other PROBLEMS item?
> (The one about exec_shield, that is.)
The exec-shield workaround kicks in if the difference between the end
of the data section and the start of the heap is greater than
MAX_HEAP_BSS_DIFF which is 1 Mbyte. But MAX_HEAP_BSS_DIFF is a value
I came up with when examining the exec-shield code in the Linux
kernel for Fedora 2. However, there is nothing preventing a new exec-
shield implementation to change this. Also, as far as I know, the
workaround has only been tested on the ix86 architecture.
So I'd propose we keep it in PROBLEMS, but we could add that Emacs
tries to handle exec-shield itself. A note on how to disable the
randomization should be added to PROBLEMS also.
Jan D.
next prev parent reply other threads:[~2005-07-02 7:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:59 New dumping problem David Kastrup
2005-03-29 19:41 ` Jan D.
2005-03-30 10:02 ` Thien-Thi Nguyen
2005-03-30 16:20 ` Richard Stallman
2005-03-30 19:17 ` Jan D.
2005-04-01 4:11 ` Richard Stallman
2005-04-01 9:54 ` Nick Roberts
2005-04-02 4:19 ` Richard Stallman
2005-03-30 0:03 ` Richard Stallman
2005-06-17 5:27 ` Katsumi Yamaoka
2005-06-17 7:07 ` Masatake YAMATO
2005-06-17 17:07 ` Masatake YAMATO
2005-06-18 1:17 ` Katsumi Yamaoka
2005-06-18 3:28 ` Masatake YAMATO
2005-06-20 0:42 ` Katsumi Yamaoka
2005-06-20 1:54 ` Masatake YAMATO
2005-06-20 17:51 ` Richard Stallman
2005-06-26 16:01 ` Masatake YAMATO
2005-06-26 17:39 ` Jason Rumney
2005-06-27 0:10 ` Masatake YAMATO
2005-06-27 5:38 ` Richard M. Stallman
2005-06-27 15:49 ` Masatake YAMATO
2005-06-30 16:26 ` Masatake YAMATO
2005-07-01 0:43 ` Katsumi Yamaoka
2005-07-01 4:02 ` Richard M. Stallman
2005-07-01 9:54 ` jhd
2005-07-01 10:29 ` Masatake YAMATO
2005-07-01 22:45 ` Richard M. Stallman
2005-07-01 22:48 ` Masatake YAMATO
2005-07-03 15:48 ` Richard M. Stallman
2005-07-01 22:45 ` Richard M. Stallman
2005-07-02 7:46 ` jhd [this message]
2005-07-03 15:48 ` Richard M. Stallman
2005-07-03 21:52 ` Jan D.
2005-06-20 17:51 ` Richard Stallman
2005-06-22 2:00 ` Katsumi Yamaoka
2005-06-22 8:20 ` Katsumi Yamaoka
2005-06-23 0:54 ` Richard M. Stallman
2005-06-23 1:08 ` Katsumi Yamaoka
2005-06-23 7:50 ` Kim F. Storm
2005-06-23 8:19 ` Katsumi Yamaoka
2005-06-23 14:28 ` Kim F. Storm
2005-06-24 0:39 ` Katsumi Yamaoka
2005-06-24 0:43 ` Katsumi Yamaoka
2005-06-24 14:18 ` Stefan Monnier
2005-06-24 16:37 ` Richard M. Stallman
2005-06-24 5:35 ` Richard M. Stallman
2005-06-24 7:09 ` Katsumi Yamaoka
2005-06-25 13:35 ` Richard M. Stallman
2005-06-17 18:45 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B4205B9F-7506-4E30-BF32-7FF49F4D1697@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.org \
--cc=yamato@redhat.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.