The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [TUHS] Emacs and undump
Date: Tue, 28 Feb 2017 01:50:55 +1100	[thread overview]
Message-ID: <CAH1jEzbZrOKxMKJOgDy=N8Tv-A+Dy4rkQOXOr3SFadn5J5vMCw@mail.gmail.com> (raw)
In-Reply-To: <20170227143302.GA15427@cowbell.employees.org>

Thanks for the stak.c it's a good idea. I'm not sure about the stack
freeing routine at the end of the file as it seems to rely on a bit of
pointer voodoo but I think I could rationalize all that.
cheers, Nick

On Feb 28, 2017 1:33 AM, "Derek Fawcus" <dfawcus+lists-tuhs at employees.org>
wrote:

> On Mon, Feb 27, 2017 at 07:12:09PM +1100, Nick Downing wrote:
> > I've been having a bit of trouble with /bin/sh (Bourne's original one)
> > for the same reason.
>  [snip]
> > Trouble is, this makes a non-stdio-using program be
> > stdio-using, in the worst case it's a non-stdio-using program that has
> > its own malloc() based on sbrk()... so we get another malloc()
> > happening in the middle, I temporarily fixed this by redirecting the
> > modern system's malloc() into the ancient system's malloc() but this
> > is a very non desirable solution. As another possibility I was
> > thinking of changing the ancient system's sbrk() into realloc() and
> > implementing a routine to relocate the heap, it obviously would have
> > to understand everything on the heap and everything that can point
> > into it.
>
> How about applying Geoff Collyer's change to the shell memory management
> routine available here:
>
>     http://www.collyer.net/who/geoff/stak.port.c
>
> DF
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170228/b79ae204/attachment.html>


  reply	other threads:[~2017-02-27 14:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.334.1488132096.3779.tuhs@minnie.tuhs.org>
2017-02-26 19:16 ` David
2017-02-26 19:28   ` Mantas Mikulėnas
2017-02-27  6:41   ` Tim Bradshaw
2017-02-27  7:19     ` Lars Brinkhoff
2017-02-27  7:26       ` Warner Losh
2017-02-27  8:12         ` Nick Downing
2017-02-27 14:33           ` Derek Fawcus
2017-02-27 14:50             ` Nick Downing [this message]
2017-02-27 15:43               ` Derek Fawcus
2017-02-27 16:43             ` Joerg Schilling
     [not found]               ` <CAH1jEzZjvOhHnbvsWcw8gbx9d_W47DbBidYd_tteCr5dC6H2ng@mail.gmail.com>
2017-02-28  0:02                 ` Nick Downing
2017-02-27 12:59       ` tfb
2017-02-27 10:35   ` Joerg Schilling
2017-02-27 15:13     ` Tony Finch
     [not found] <mailman.342.1488180370.3779.tuhs@minnie.tuhs.org>
2017-02-27 10:24 ` Johnny Billquist
2017-02-27 10:30   ` Lars Brinkhoff
2017-02-27 10:47     ` Johnny Billquist
2017-02-27 14:04       ` Arthur Krewat
2017-02-28 11:55         ` Ronald Natalie
     [not found] <mailman.346.1488208394.3779.tuhs@minnie.tuhs.org>
2017-02-27 20:09 ` Johnny Billquist
2017-02-27 20:26   ` Lars Brinkhoff
2017-02-27 21:06     ` Johnny Billquist

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='CAH1jEzbZrOKxMKJOgDy=N8Tv-A+Dy4rkQOXOr3SFadn5J5vMCw@mail.gmail.com' \
    --to=downing.nick@gmail.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.
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 NNTP newsgroup(s).