Sergei Gorelkin wrote:
11.12.2012 1:27, Sven Barth пишет:
It's putting a significant number of AT_NONE entries into the table, and
the first one it tries to take out (which obviously isn't the first
entry in the list) causes the internal error. When being put in, this
entry had a call stack like
#0 TASMDATA__REFASMSYMBOL('PBGetCatInfoSync', <error reading variable>)
at aasmdata.pas:443
I had also made out this location as the only plausible one for these
AT_NONE entries. Maybe the
external handling was changed since Mac OS last worked and the MPW
writer wasn't adjusted then...
Well, all ELF targets emit external symbols in object files with
STT_NOTYPE type field, which corresponds to AT_NONE internal
representation. COFF targets also accept this, although recent GCC/MinGW
versions are marking external functions with proper type.
I tried working through different backends to see if there was handling
for AT_NONE in the ones that were working, but couldn't see anything
obvious.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel