On 30.08.2012 00:13, Graeme Geldenhuys wrote:
> Signal received. Signal: SIGSEGV, Segmentation fault.
>
> #0 0040E1BB :0 SYSTEM_WAITFREE_FIXED$PMEMCHUNK_FIXED$POSCHUNK()
> #1 01FB8D3C :0 ??()
> #2 0040C51A :0 fpc_finalize()
> #3 0001 :0 ??()
> #4 0040AD2A :0 SYSTEM_TOBJECT_$__CLEANUPINST
On 29/08/12 23:23, Jonas Maebe wrote:
The first thing you can try is to compile with -gh, hoping that it
will abort in a place closer to the cause of the problem. -CRr is
also a very useful debugging switch.
Thanks for the detailed information. The bug is not fixed yet, but I did
eventually
On 30 Aug 2012, at 00:13, Graeme Geldenhuys wrote:
> ---
> Signal received. Signal: SIGSEGV, Segmentation fault.
>
> #0 0040E1BB :0 SYSTEM_WAITFREE_FIXED$PMEMCHUNK_FIXED$POSCHUNK()
> #1 01FB8D3C :0 ??()
> #2 0040C51A :0 fpc_finalize()
> #3 0001 :0 ??()
> #4 0
Hi,
I hope somebody knows more about GDB that I. I'm trying to debug an
error in one of our Master Maths projects. This error only occurs under
Windows, where it bombs out at random times (in a specific section of
our product) with a "Segmentation Fault" error. GDB pauses the program
at that
