ESP8266 Developer Zone

Re: SDK 1.4 issue os_zalloc

2015-09-23T09:38:08+08:00

The prototype changed with the memory tracing in SDK 1.4

Statistics: Posted by tve — Wed Sep 23, 2015 9:38 am

Re: SDK 1.4 issue os_zalloc

2015-09-23T00:05:29+08:00

Yes indeed, it looks this function now finally has a proper prototype and the prototype guessed by the author apparently was wrong.

This is actually a good thing, because improperly prototyped function calls can cause crashed and other unpredictable behaviour.

Statistics: Posted by eriksl — Wed Sep 23, 2015 12:05 am

Re: SDK 1.4 issue os_zalloc

2015-09-22T03:07:28+08:00

When using SDK supplied APIs try and find the corresponding C header file that contains the prototype definitions. For os_ functions, this is the file called "mem.h" contained in /include/mem.h. Looking at that file, we will find that the definitions for items such as "os_zalloc" have been defined as macros with additional parameters for memory leak debugging.

I'd suggest including mem.h and removing any previously manually defined definitions of os_ functions that you may have coded.

Neil

Statistics: Posted by kolban — Tue Sep 22, 2015 3:07 am

SDK 1.4 issue os_zalloc

2015-09-22T02:30:23+08:00

Hi

Up to now, various SDKs have been drop-in and recompile - this time with 1.4 I get an error when compiling this (which sadly I did not write so I don't want to mess it up).

void ICACHE_FLASH_ATTR QUEUE_Init(QUEUE *queue, int bufferSize)
{
queue->buf = (uint8_t*)os_zalloc(bufferSize);
RINGBUF_Init(&queue->rb, queue->buf, bufferSize);
}

mqtt/queue.c:42:2: error: too many arguments to function 'pvPortZalloc'
queue->buf = (uint8_t*)os_zalloc(bufferSize);
^

Statistics: Posted by scargill — Tue Sep 22, 2015 2:30 am