[En-Nut-Discussion] NutHeapAvailable() question

[Alexander Baranov]

Thanks, Henrik and Harald.
I discovered the bug. It was a symbol "-" printed out from another thread. 
Sorry for disturbing you.
Alexander.
----- Original Message ----- 
From: "Harald Kipp" <harald.kipp at egnite.de>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Friday, September 29, 2006 12:00 PM
Subject: Re: [En-Nut-Discussion] NutHeapAvailable() question


> Alexander,
>
> ..or a problem of the uart driver...
>
> Another thing you could do is to check the .map file.
>
> Here's the API tree for fprintf:
> http://www.ethernut.de/api/group__xgCrtStdio.html
>
> Down to _write, all routines should be supplied by libnutcrt.a and
> must not be provided by any WinAVR library. The final dev_write
> is the link to the UART driver, typically contained in libnutarch.a.
>
> Btw. how does your fopen() look like?
>
> Harald
>
>
> At 11:28 29.09.2006 -0400, you wrote:
>
>>Then I tried
>>int amama = 12;
>>fprintf(uart, "\n\r%d, %d, %d\n\r", amama, amama, amama );
>>and also got
>>-1, 12, 12
>>So the reason is not in NutHeapAvailable() but in some fprintf issues.
>>Regards
>>Alex.
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>
>