[fpc-pascal] Ansistrings under Android

Dejan Boras de_jean_7777 at yahoo.com
Tue Feb 22 23:03:06 CET 2011

It's a problem I can work around, but I'm not sure how this affects the functionality of ansistrings.

----- Original Message -----
From:Thomas Schatzl <tom_at_work at gmx.at>
To:FPC-Pascal users discussions <fpc-pascal at lists.freepascal.org>
Sent:Tuesday, February 22, 2011 10:44 PM
Subject:Re: [fpc-pascal] Ansistrings under Android


On Tue, 22 Feb 2011 13:34:06 -0500, Andrew Haines <AndrewD207 at aol.com>
> On 02/22/11 12:06, de_jean_7777 wrote:
>> Now that I have a working fpc crosscompiler for Android, and all the
>> code runs ok, I encountered another problem. Namely working with
>> ansistrings causes crashes. For example, in a simple test, calling the
>> str() routine will cause a crash due to a run-time 216 error (general
>> protection fault). I've also noticed that crashes can occur upon
>> exit, when ansistrings are freed automatically. I thought that using
>> C memory manager (cmem) might help, but there is no difference.
>> For some reason, units are not initialized under a android shared
>> library, so I call internal_initializeunits() myself in the JNI_OnLoad
>> which is called automatically by the JNI, and is called before any
>> routine.

The shared library startup code for ARM is broken (well, from the svn it
seems that it never worked), it does not set up the environment variables
and call the pascal unit initialization routine.

This is a "known" issue in so far as there are some testsuite tests
(tw8730) that fail because of that.


fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org

More information about the fpc-pascal mailing list