[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140221163639.GP23551@port70.net>
Date: Fri, 21 Feb 2014 17:36:40 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Re: Removing sbrk and brk
* Daniel Cegie?ka <daniel.cegielka@...il.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
> # grep -r sbrk /usr/bin/
> Binary file /usr/bin/readelf matches
> Binary file /usr/bin/as matches
> Binary file /usr/bin/addr2line matches
> Binary file /usr/bin/c++filt matches
> Binary file /usr/bin/ld matches
> Binary file /usr/bin/objdump matches
> Binary file /usr/bin/size matches
> Binary file /usr/bin/ar matches
> Binary file /usr/bin/objcopy matches
> Binary file /usr/bin/elfedit matches
> Binary file /usr/bin/strings matches
> Binary file /usr/bin/ld.bfd matches
> Binary file /usr/bin/strip matches
> Binary file /usr/bin/gdb matches
> Binary file /usr/bin/nm matches
> Binary file /usr/bin/ranlib matches
>
> eg ex/vi doesn't work with new musl (git) - sbrk is used internally:
>
> 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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
