Michael Van Canneyt wrote:
> > What time stamps are in use on the various platforms?
>
> Too various. I suggest using simply TDateTime. It has microsecond
> resolution, which should be more than enough. It offers the additional
> advantage that no transformations are necessary for display & compa
> Mattias Gaertner wrote:
>> Since a week I get strange, sporadic errors with current fpc.
>> For example:
>>
>> TMainIDE.DoSaveAll
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> $0a9a0c08 in ?? ()
>> (gdb) bt
>> #0 $0a9a0c08 in ?? ()
>> First symbol in segment of executable not a s
> Since a week I get strange, sporadic errors with current fpc.
> For example:
>
> TMainIDE.DoSaveAll
>
> Program received signal SIGSEGV, Segmentation fault.
> $0a9a0c08 in ?? ()
> (gdb) bt
> #0 $0a9a0c08 in ?? ()
> First symbol in segment of executable not a source symbol
>
> That's why I think,
Mattias Gaertner wrote:
Since a week I get strange, sporadic errors with current fpc.
For example:
TMainIDE.DoSaveAll
Program received signal SIGSEGV, Segmentation fault.
$0a9a0c08 in ?? ()
(gdb) bt
#0 $0a9a0c08 in ?? ()
First symbol in segment of executable not a source symbol
That's why I thi
Since a week I get strange, sporadic errors with current fpc.
For example:
TMainIDE.DoSaveAll
Program received signal SIGSEGV, Segmentation fault.
$0a9a0c08 in ?? ()
(gdb) bt
#0 $0a9a0c08 in ?? ()
First symbol in segment of executable not a source symbol
That's why I think, it's a compiler bug
