From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Re: Removing sbrk and brk
Date: Fri, 21 Feb 2014 17:47:05 +0100 [thread overview]
Message-ID: <CAPLrYEQSv1kLbJRkAQFGLQFZcvY94LHcu39DfFUsoAYondAvwQ@mail.gmail.com> (raw)
In-Reply-To: <20140221163639.GP23551@port70.net>
2014-02-21 17:36 GMT+01:00 Szabolcs Nagy <nsz@port70.net>:
> * Daniel Cegie?ka <daniel.cegielka@gmail.com> [2014-02-21 17:03:36 +0100]:
>> And what do we do with failures when sbrk is used?
>>
>
> most of these only call sbrk(0) which is supported
ok, thank you for the information.
>> http://ex-vi.cvs.sourceforge.net/viewvc/ex-vi/ex-vi/ex_subr.c?revision=1.8&view=markup
>>
>
> the "old musl" did not support sbrk either (the cited code uses it
> with malloc), the "new musl" just helps you find the bug more easily
ex/vi doesn't work with the new musl. Too bad, because it is the
traditional unix ex/vi. Maybe Gunnar Ritter still fixes bugs.
best regards,
Daniel
next prev parent reply other threads:[~2014-02-21 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 23:40 Rich Felker
2013-12-22 2:15 ` Luca Barbato
2013-12-22 17:58 ` Richard Pennington
2013-12-22 18:21 ` Luca Barbato
2013-12-22 18:48 ` Szabolcs Nagy
2013-12-22 21:55 ` Christian Neukirchen
2013-12-23 4:46 ` Rich Felker
2014-01-02 22:03 ` Rich Felker
2014-01-03 11:51 ` Thorsten Glaser
2014-01-03 12:59 ` Daniel Cegiełka
2014-01-03 17:33 ` Rich Felker
2014-01-03 18:19 ` Rich Felker
2014-01-03 19:03 ` Rich Felker
2014-01-06 14:51 ` Thorsten Glaser
2014-01-06 22:40 ` Rich Felker
2014-01-07 9:43 ` Thorsten Glaser
2014-01-07 16:06 ` Rich Felker
2014-01-07 22:00 ` Rich Felker
2014-02-21 16:03 ` Daniel Cegiełka
2014-02-21 16:36 ` Szabolcs Nagy
2014-02-21 16:47 ` Daniel Cegiełka [this message]
2014-02-21 17:09 ` Rich Felker
2014-02-21 22:34 ` Daniel Cegiełka
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=CAPLrYEQSv1kLbJRkAQFGLQFZcvY94LHcu39DfFUsoAYondAvwQ@mail.gmail.com \
--to=daniel.cegielka@gmail.com \
--cc=musl@lists.openwall.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 public inbox
https://git.vuxu.org/mirror/musl/
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).