On 9 June 2014 08:40, Yoann Padioleau wrote:
> I think I've found a possible situation where we call two times free on
> the same pointer.
> in sysexec() there is essentially
>
the only correct way to write these is not to rely on nil values or not,
but immediately after the allocation, include
Hi,
I think I've found a possible situation where we call two times free on the
same pointer.
in sysexec() there is essentially
sysexec(...) {
…
if(waserror()){
free(file0);
free(elem);
nexterror();
}
for(;;){
