unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ashish.is@lostca.se (Ashish SHUKLA)
Cc: 24892@debbugs.gnu.org
Subject: bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture
Date: Mon, 07 Nov 2016 17:19:38 +0200	[thread overview]
Message-ID: <837f8fiagl.fsf@gnu.org> (raw)
In-Reply-To: <8660nzkevm.fsf@lostca.se> (ashish.is@lostca.se)

> From: ashish.is@lostca.se (Ashish SHUKLA)
> Date: Mon, 07 Nov 2016 11:31:17 +0530
> 
> As mentioned in the subject, {,s}brk syscalls are removed from arm64
> architecture on FreeBSD 11.x[1].

Are they mad?

Thanks for reporting this.

A "fix" for memory-limit is simple, like NS already does (but we will
need a configure-time test for sbrk).  The issue with unexelf is more
serious.  I guess we will have to use mmap (or the result of the
existing call to it) instead?





  reply	other threads:[~2016-11-07 15:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  6:01 bug#24892: {s, }brk removed from FreeBSD 11.x and later, arm64 architecture Ashish SHUKLA
2016-11-07 15:19 ` Eli Zaretskii [this message]
2016-11-08 17:54 ` Paul Eggert
2016-11-08 20:11   ` Eli Zaretskii
2016-11-08 21:41     ` Paul Eggert
2016-11-09  3:34       ` Eli Zaretskii
2016-11-09  8:27         ` Paul Eggert
2016-11-09 15:49           ` Eli Zaretskii
2016-11-10  1:47             ` Paul Eggert
2016-11-10 16:13               ` Eli Zaretskii
2016-11-10 16:59                 ` Paul Eggert
2016-11-10 17:24                   ` Eli Zaretskii
2016-11-10  0:22       ` Richard Stallman
2016-11-10  1:40         ` Paul Eggert
2016-11-09  4:29 ` Ashish SHUKLA
2016-11-09  8:26   ` Paul Eggert
2016-11-09  9:46     ` Andreas Schwab
2016-11-09 15:50       ` Eli Zaretskii
2016-11-09 17:52       ` Paul Eggert
2016-11-10  9:52         ` Andreas Schwab
2016-11-10 16:23           ` Paul Eggert
2016-11-10 17:00             ` Andreas Schwab
2016-11-10 17:22               ` Paul Eggert
2016-11-10 17:33                 ` Andreas Schwab
2016-11-11  2:48                   ` Paul Eggert
2016-11-17 17:27                     ` Eli Zaretskii
2016-11-18 12:29                       ` Ashish SHUKLA
2016-11-18 16:21                         ` Paul Eggert
2016-11-18 20:20                           ` Ed Maste
2016-11-18 20:23                           ` Brooks Davis
     [not found]                           ` <CAPyFy2AL_OZWYpp+tiLSro_3WK1-H8Pdjy4-ZhUQChMQqageUw@mail.gmail.com>
2016-11-18 22:22                             ` Paul Eggert
2016-11-19  6:57                               ` Eli Zaretskii
2016-11-19  7:20                               ` Eli Zaretskii
2017-09-02 13:37                                 ` Eli Zaretskii
2016-11-09 13:23     ` Ashish SHUKLA

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=837f8fiagl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24892@debbugs.gnu.org \
    --cc=ashish.is@lostca.se \
    /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).