On 03 Jun 2010, at 18:46, José Mejuto wrote:
> I was only able to set a break over _haltproc and it catches the exit
> with this backtrace:
>
> #0 0x082da470 in SI_C21__FPC_LIBC21_HALTPROC ()
> #1 0x080779d4 in SYSTEM_SYSTEM_EXIT ()
> #2 0x080700da in SYSTEM_DO_EXIT ()
> #3 0x080700fa in SYS
Hello FPC-Pascal,
Thursday, June 3, 2010, 3:31:31 PM, you wrote:
JM> You can try putting breakpoints on FPEXIT, _haltproc and _exit (the
JM> last one only exists if libc is linked, but that's definitely the case
JM> here; note that all of them are case-sensitive). That should catch
JM> most exits
Hello FPC-Pascal,
Thursday, June 3, 2010, 2:26:58 PM, you wrote:
>> Did you try disabling floating point exceptions? A lot of C code
>> assumes that floating point exceptions are disabled (since that's
>> what the C library does on startup).
JM> Another possible problem can be the fact that FPC
Hello FPC-Pascal,
Thursday, June 3, 2010, 8:55:47 AM, you wrote:
MVC> Are you cooperating with Phil on this ?
Just to keep the message in thread, I re-answer this message.
After a bit more debugging I found something strange (again it could
be fpc related or not, I'm not sure). This is the firs
Hello FPC-Pascal,
Thursday, June 3, 2010, 10:24:43 AM, you wrote:
>> Did you try disabling floating point exceptions? A lot of C code assumes that
>> floating point exceptions are disabled (since that's what the C library does
>> on startup).
MVC> Aha. And how do I do that ?
Set8087CW($133F); ?
Hello FPC-Pascal,
Thursday, June 3, 2010, 10:08:00 AM, you wrote:
>> When I was debugging it (linux 64 bit) , the whole application
>> stopped on a floating point error somewhere in mozilla's Javascript
>> engine; I never got
>> around to debugging that.
JM> Did you try disabling floating point e
Hello FPC-Pascal,
Thursday, June 3, 2010, 8:55:47 AM, you wrote:
MVC> Are you cooperating with Phil on this ?
Yes. Phil is not supporting it now so I had added some improvements.
MVC> When I was debugging it (linux 64 bit) , the whole application stopped on a
MVC> floating point error somewhere
