I do not undertand why this happens, because I chose "N" to the question:
"use mlockall to prevent swapping ? (Y/N) " -> "N"
This is a trivial bug. There should have been a test if(ui.memloc==0)
Ok. The xz() function has been a very efective way of finding where the
crash occured. Thank
Hi Ramiro,
> After some "compilation and xz iterations", I have found that the
> funcion that completly crashes my computer is mlockall(), called from
> function lir_lock_mem() in lsys.c.
>
> lir_lock_mem() is called from main() in lmain.c
>
>
> The call to mlockall() never returns and crashe
Hi Leif,
Forgot to post the debugging "xz":
int lir_lock_mem(void)
{
int i,k;
xz("lir_lock_mem_1");
i= mlockall(MCL_CURRENT);
xz("lir_lock_mem_2");
if(i==0)return 0;
k=errno;
munlockall();
errno=k;
return i;
}
More information about the mlockall issue.
This "dirty" code modificati
Ramiro Aceves wrote:
[EMAIL PROTECTED] wrote:
Hi Ramiro,
The way I locate this kind of errors is th change "DUMPFILE",
now in vernr.h, to 1.
Hello Leif,
I have done the debugging you suggested.
After some "compilation and xz iterations", I have found that the
funcion that completly crash
[EMAIL PROTECTED] wrote:
Hi Ramiro,
The way I locate this kind of errors is th change "DUMPFILE",
now in vernr.h, to 1.
Hello Leif,
I have done the debugging you suggested.
After some "compilation and xz iterations", I have found that the
funcion that completly crashes my computer is mlocka
[EMAIL PROTECTED] wrote:
Hi Ramiro,
The way I locate this kind of errors is th change "DUMPFILE",
now in vernr.h, to 1.
Then add statements xz("comment");
between code statement statements.
xz={fprintf(dmp,"%s\n",agr);fflush(dmp);sync();}
When the computer has rebooted, the last line in the fil
Hi Ramiro,
The way I locate this kind of errors is th change "DUMPFILE",
now in vernr.h, to 1.
Then add statements xz("comment");
between code statement statements.
xz={fprintf(dmp,"%s\n",agr);fflush(dmp);sync();}
When the computer has rebooted, the last line in the file
dmp is the last xz statem
