[jira] [Resolved] (THRIFT-4454) Large writes/reads may cause range check errors in debug mode
[ https://issues.apache.org/jira/browse/THRIFT-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Geyer resolved THRIFT-4454. Resolution: Fixed Committed. > Large writes/reads may cause range check errors in debug mode > - > > Key: THRIFT-4454 > URL: https://issues.apache.org/jira/browse/THRIFT-4454 > Project: Thrift > Issue Type: Bug > Components: Delphi - Library >Affects Versions: 0.11.0 >Reporter: Jens Geyer >Assignee: Jens Geyer >Priority: Major > Fix For: 0.12.0 > > > The pipes code contains a few casts using the {{PByteArray}} pointer type. > The underlying array {{TByteArray}} is defined as {code} > type TByteArray = array [0..32767] of Byte; > {code} > With range checks enabled, any access to indices > 32767, even correct ones, > result in an range check exception. It may be worth noting that the code is > otherwise entirely correct (i.e. no buffer overruns). It is really only the > type cast that introduces the failing constraint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (THRIFT-4454) Large writes/reads may cause range check errors in debug mode
[ https://issues.apache.org/jira/browse/THRIFT-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Geyer resolved THRIFT-4454. Resolution: Fixed Committed > Large writes/reads may cause range check errors in debug mode > - > > Key: THRIFT-4454 > URL: https://issues.apache.org/jira/browse/THRIFT-4454 > Project: Thrift > Issue Type: Bug > Components: Delphi - Library >Affects Versions: 0.11.0 >Reporter: Jens Geyer >Assignee: Jens Geyer > Fix For: 0.12.0 > > > The pipes code contains a few casts using the {{PByteArray}} pointer type. > The underlying array {{TByteArray}} is defined as {code} > type TByteArray = array [0..32767] of Byte; > {code} > With range checks enabled, any access to indices > 32767, even correct ones, > result in an range check exception. It may be worth noting that the code is > otherwise entirely correct (i.e. no buffer overruns). It is really only the > type cast that introduces the failing constraint. -- This message was sent by Atlassian JIRA (v6.4.14#64029)