[fpc-pascal] access violations on new ARM hardware

Björn Schreiber news.bs at drigus.de
Wed Jan 28 09:30:55 CET 2015

Am 27.01.2015 um 17:58 schrieb Marco van de Voort:

> First narrow it down to the exact line that causes the problem. E.g. copy
> relevant parts of sysutils into a program that only uses system, and then
> start testing, till you know which line provokes the problem.

   What I can say at this time is that the first access violation 
happens at the line


in the function SysUtils.GetLocalStr in an empty FPC program only 
including the unit SysUtils. But I suppose the problem lies elsewhere.

More information about the fpc-pascal mailing list