Re: Exception handling??
Ok here's the clue:
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
An unhandled exception! Any reasonable modern language would convert this OS exception to an exception that it can handle - the same way as it would handle any other natively thrown exceptions.
As far as the ApplyGlyphFeatureTags function goes - the original programmer *should* have tested the pointer better - rather than just comparing it to nil. In the old days on Windows we used to use IsBadReadPtr to do this - but that's now seriously deprecated, and according to MSDN you're meant to use structured exception handling instead.
In this case, handling the exception simply by logging it, and applying some default glyph feature tag sounds like a reasonable approach.
>> If you think this problem has anything to do with exception handling, then you really, really don't know what you are talking about.