Glenn Howes wrote:
I applied your fix and I got further, at least, before crashing again. Running… Program received signal: "EXC_BAD_ACCESS".
Unable to disassemble _p_Unbind.
(partial stack trace) _p_Unbind _p_AssignFile _p_Assign (my code)
Does this appear to be a problem with initialization or linking?
I can't say without knowing more about the application and circumstances (and also see the crash log from the /Applications/Utilities/Console utility).
You can try to locate the problem yourself in Xcode
- to enable debug info for Pascal application code, add "-g" to the
gpc (or gp) command line options
- to get useful debug info for the GPC runtime library, build the
Pascal compiler from sources (see my website, it's not difficult anymore)
- in Xcode, uncheck the "load symbols lazily" preference setting.
Still, I can't resist to fire a blind shot in the dark - what kind of strings are you using to interface between Pascal and C ? If you are using UCSD-Pascal strings (\p in the Apple gcc compiler and Str255, Str63 or Str31 in the Mac OS X Pascal interfaces) then any interfacing between Pascal and C must be done with const or var parameters, value parameters will crash (the UCSD-Pascal strings in the Mac OS X Pascal interfaces are tricked).
A question, did linking GPC to C/C++ on powerpc work without adding darwin-fpsave.o ? Not related to the above problem, just curious.
Regards,
Adriaan van Os