Hello,
ah, sure. I did not connect tests/malloc to the path in RIOT. Thanks for the
clarification.
Raphael
On Jan 30, 2015, at 4:07 PM, Benjamin Valentin benpi...@zedat.fu-berlin.de
wrote:
On 24.01.2015 11:04, Hiesgen, Raphael wrote:
Hello Benjamin,
I'm not sure what that
On 24.01.2015 11:04, Hiesgen, Raphael wrote:
Hello Benjamin,
I'm not sure what that documentation is based on though, running tests/malloc
will allocate and free all available memory just fine.
may I ask how you tested this?
I just flashed the test to my board (not stm32f4discovery, but
Hello Benjamin,
I'm not sure what that documentation is based on though, running tests/malloc
will allocate and free all available memory just fine.
may I ask how you tested this?
Raphael
___
devel mailing list
devel@riot-os.org
Hi Raphael,
for the native-stuff you have to ask Ludwig for the specifics as to of why,
but most of the hosts system's implementation of standard functions are
wrapped. I think this was because our POSIX interface would otherwise
colide with the system's POSIX interface. As for the other boards
Hi,
On Thu, Jan 22, 2015 at 10:56:22AM +0100, Martine Lenders wrote:
for the native-stuff you have to ask Ludwig for the specifics as to of why,
but most of the hosts system's implementation of standard functions are
wrapped. I think this was because our POSIX interface would otherwise
colide
