Bad declaration of __tm_gmtoff inside tm record from timeh.inc
Original Reporter info from Mantis: FPCCore
-
Reporter name: FPC core team
Original Reporter info from Mantis: FPCCore
- Reporter name: FPC core team
Description:
Kylix have field __tm_gmtoff on place, where you have tm_gmtoff field in tm record. Your tm record have __tm_gmtoff field on end of this structure.
So, when I need to work with __tm_gmtoff field, then it works under Kylix, but under FPC it read value from bad memory place!
Right will be if fields:
__tm_gmtoff : longint;
__tm_zone : Pchar;
have same memory place as your fields:
tm_gmtoff : longint;
tm_zone : Pchar;
Additional information:
Reporter: Lukas Gebauer
EMail: gebauerl at mlp dot cz
Mantis conversion info:
- Mantis ID: 5823
- OS: Linux
- Version: 1.9.8
- Fixed in version: 1.9.9