>{
> _free(p);
> p=(void *)0;
> }
I think we should find the instruction that crash, when you set a value to 0 and it work then, this remember me on the wrong autogen stub entry for strcat.it use strncpy.
and this function use 1 parameter more and work diffrent.so it happen that this parameter get a random len value which only for log message output not good.
if this set to 0 help always is not clear, there can crash happen maybe on larger dir or so.
I have currently not much time to do.
so my hot guess is, that there is a function that have wrong stub and this is now show, because malloc now do inside func use more stack and registers.so the stack values and register are diffrent than before
My guess is this function sit after a malloc and is not often used in other chdk code, and it have on the autostub guess a a % value below 80%.
exmem really work stable what i do, i use it often and i like to photograph.
only problem is the filebrowser.and this problem happen too when no exmem is need.
I think it is best when exmem give us more memory, that we use for all string functions C code and no Canon functions, this avoid problems on newer Cams that autodetect stub code do wrong, at least with strcat
I see in all new firmware its wrong detect, but some have silenty correct it and not information other.
too bad that nobody other as me add in this thread Porting Problems and solutions, what find on wrong detect functions, or other porting Problems and fixes need on newer Camera.
http://chdk.setepontos.com/index.php?topic=6037.0there are 125 reads now,but nobody write what problem he get and fix.
sure it cost a little time to write, but all in all porting go lots faster, if not everybody need Reinventing the wheel ;-)
