[gambit-list] ___setup memory corruption(?) on iPhone

mikel evins mevins at me.com
Fri Jun 8 11:56:27 EDT 2012


On Jun 8, 2012, at 10:41 AM, Marc Feeley wrote:

> 
> On 2012-06-06, at 6:57 PM, Kirill Zorin wrote:
> 
>> Hi all,
>> 
>> I've built (a slow version of) Gambit with llvm-gcc 4.2 on Mac OS X, targeted for the iPhone, using the build-gambit-iOS script, for the iOS 5.1 SDK. (I can't build it with latest clang, because for whatever reason Gambit's configure exits with various autoconf-related errors when clang is used.)
> 
> Can you please report to the ML what those errors are?

I saw similar problems using 4.6.6 built for iOS with clang (Xcode 4.3.2). Unfortunately, I can't tell you much about the errors. They were segfaults that occurred at random (short) intervals after the call to setup, and that's about all I know. Commenting out the call to setup (and, naturally, anything that depended on it) cured the segfault.

The built apps crashed hard and left no information behind. In fact, the only evidence that they had occurred at all (besides the quick disappearance of the app form the device screen) was a single line each time in the console log reporting a segfault.

One other thing I can report is that I had NSLog statements in code after the segfaults for testing and debugging, and some of those ran sometimes before the segfault. They printed the results of calls into the Gambit runtime, so we can infer that Gambit setup managed to build enough of the Gambit environment to carry out some evaluations before hitting whatever broken part caused the segfault.


More information about the Gambit-list mailing list