>
> The problem appears to be in Roxen itself tho or hardware, as I
> managed to catch a console error message:
>
> *** glibc detected *** malloc(): memory corruption (fast):
> 0x00000000010c524e ***
>
This is apparently the feature of glibc to report & stop the program.
If MALLOC_CHECK_ is explicitly set a value other than 0, this
causes glibc to perform more tests that are more extensive than the
default, and may impact performance.
Should you have a program from a third party ISV that triggers
these corruption checks and displays a message, you should file a
defect report with the application's vendor, since this indicates a
serious bug
Setting env var to MALLOC_CHECK_=1 should generate error msg but not
abort the program.
Unfortunately, it doesn't generate much on Roxen startup/run except a
repeated msg:
malloc: using debugging hooks
and it STILL aborts program, indicating the problem is perhaps even
more serious as appears.
Now to rewrite my <?pike?> to other things... *sigh*
|