[Pythonmac-SIG] Interpreting a crash dump?

[Robin Becker]

A 10.2 client has crashes using our dylib packaged python application.
The dylib was built using the traditional configure make dance starting
with a standard Python 2.2.2 tgz, then freeze was hacked to make the
output a dylib rather than an executable.

The client is suggesting a mismatch between the quark version of strncpy
and the one that python wants to use.

The following strategies are suggested

1) build the app as a static library.
2) build the dylib with all dependencies statically linked.
3) Build the application as a normal python embedding dll (ie make use
of the standard OS X Python (presumably now based on 2.3).

I assume that both 1) and 2) are feasible, but am a bit unsure how using
standard python will help to alter the way in which stuff gets linked
together. I'm not a mach expert, but is there a way to get my dylib to
link to the 'correct' strncpy etc etc?


********************** CRASH TRACE ****************************

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000005

Thread 0 Crashed:
0   com.quark.QuarkXPress               0x00528158 strncpy + 0x10
1   lib_rl_embed.dylib                  0x0822b848 inittime + 0x150
(timemodule.c:664)
2   lib_rl_embed.dylib                  0x08216050 init_builtin + 0x21c
(import.c:1464)
3   lib_rl_embed.dylib                  0x08215d28 load_module + 0x238
(import.c:1402)
4   lib_rl_embed.dylib                  0x08216c5c import_submodule +
0x170 (import.c:1910)
5   lib_rl_embed.dylib                  0x0821673c load_next + 0x148
(import.c:1771)
6   lib_rl_embed.dylib                  0x082184c0 import_module_ex +
0x5c (import.c:1618)
-- 
Robin Becker