From: Ken Raeburn <raeburn@raeburn.org>
To: David Kuehling <dvdkhlng@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Some OpenWrt port related problems
Date: Sun, 2 Jan 2011 15:35:27 -0500 [thread overview]
Message-ID: <CDA7E7B6-6AC7-4985-9C2E-98E8FBDC0B14@raeburn.org> (raw)
In-Reply-To: <87pqsfcsyc.fsf@snail.Pool>
On Jan 2, 2011, at 08:53, David Kuehling wrote:
> Well, if those pages are not modified, no memory is needed from the OS
> anyway (i.e. copy-on-write/lazy copy). Just that linux VM manager seems
> to usually check whether it has enough pages just-in-case.
>
> Similar problems seem to crop up with fork();exec() inside emacs. So
> enabling overcommitting on the NanoNote may be a good thing in general.
Eh.. I've never been convinced that it's a good thing. I like the fact that mmap/malloc can fail, and give you a chance to recover, rather than simply having a process blown out of the water when it turns out that a page isn't actually available after all. But that's just me....
> $ readelf -t /usr/bin/emacs
>
> There are no sections in this file.
>
> :)
>
> Could it be that 'sstrip' (that's no typo, it's not vanilla 'strip')
> used for openwrt packages causes collateral damage here? Emacs won't be
> the only package effected.
Okay, then you are doing something different... I don't know how unexelf.c is going to handle a file with no section headers. As best I recall, they're not critical for execution, but unexelf.c may be making additional assumptions based on how other systems tend to operate. Ideally, I think it should be possible to just extent the loadable data sections, but that's not how unexelf.c operates. If you can bypass 'sstrip' for a package, or just one executable in the package (emacsclient should be fine to strip, for example), that might fix the problem and allow you to have it dump during installation.
Ken
next prev parent reply other threads:[~2011-01-02 20:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:15 Some OpenWrt port related problems David Kuehling
2010-12-28 19:36 ` Stefan Monnier
2010-12-28 21:12 ` David Kuehling
2010-12-28 22:02 ` Stefan Monnier
2010-12-29 9:37 ` David Kuehling
2010-12-29 7:47 ` Richard Stallman
2010-12-29 9:28 ` David Kuehling
2010-12-30 4:08 ` Ken Raeburn
2011-01-01 14:20 ` David Kuehling
2011-01-01 15:06 ` Andreas Schwab
2011-01-01 15:34 ` Eli Zaretskii
2011-01-02 1:35 ` Ken Raeburn
2011-01-02 13:53 ` David Kuehling
2011-01-02 14:44 ` Stefan Monnier
2011-01-02 14:55 ` David Kuehling
2011-01-02 20:35 ` Ken Raeburn [this message]
2011-01-02 21:12 ` David Kuehling
2011-01-03 9:32 ` David Kuehling
2010-12-30 16:06 ` 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=CDA7E7B6-6AC7-4985-9C2E-98E8FBDC0B14@raeburn.org \
--to=raeburn@raeburn.org \
--cc=dvdkhlng@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.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 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.