Re: [fpc-devel] RangeCheck error in sysutils.FILEGETATTR

2010-03-29 Thread Martin
On 29/03/2010 10:11, cobines wrote: Maybe it's because GetFileAttributes returns DWORD (unsigned) but FileGetAttr's result is Longint (signed). When directory not exists result is DWORD(-1) = 0x which is outside of Longint range. Shall I create a bug report?

Re: [fpc-devel] RangeCheck error in sysutils.FILEGETATTR

2010-03-29 Thread cobines
Maybe it's because GetFileAttributes returns DWORD (unsigned) but FileGetAttr's result is Longint (signed). When directory not exists result is DWORD(-1) = 0x which is outside of Longint range. -- cobines ___ fpc-devel maillist - fpc-devel@list

[fpc-devel] RangeCheck error in sysutils.FILEGETATTR

2010-03-28 Thread Martin
I have no idea, if this is an FPC or Lazarus, though it seems to be FPC / RTL. I get the following exception, with trunk, revision 15038. Build with range check -Cr -Co -Ct It happens when calling FILEGETATTR with the name of a not existing directory. The stacktrace is from Lazarus, checkin