Le 6 juil. 2010 à 22:49, Jeffrey J. Early a écrit :
> Importantly, I'm not calling any code framework A that depends on framework
> B. Because of this, in 32-bit mode, it ended up being totally okay that
> framework B was missing (presumably because it never had to resolve any
> symbols from th
Much thanks to the three of you for your responses, with your help I was able
to solve the problem. It was a dumb mistake on my part that was exposed due to
different behavior in how dyld works (apparently?!).
I have dependencies on a bunch of my own frameworks, and a few third party
frameworks
Jeffrey J. Early wrote:
- The crash does *not* occur when the application (either release
or debug build) is launched within Xcode.
- The crash *does* occur if I launch the app with gdb from the
command line (same stack trace).
Inspect and then change things about your executable's runtime
On Jul 6, 2010, at 11:47 AM, Jeffrey J. Early wrote:
> I just transitioned my (primarily Cocoa based) code from building 32-bit
> i386/PPC, to also include x86_64. Unfortunately, when launching the 64-bit
> version I'm getting a crash at launch and I can't figure out how to debug it.
> Stack tr
On Tue, Jul 6, 2010 at 9:47 AM, Jeffrey J. Early
wrote:
> I just transitioned my (primarily Cocoa based) code from building 32-bit
> i386/PPC, to also include x86_64. Unfortunately, when launching the 64-bit
> version I'm getting a crash at launch and I can't figure out how to debug it.
> Stack
I just transitioned my (primarily Cocoa based) code from building 32-bit
i386/PPC, to also include x86_64. Unfortunately, when launching the 64-bit
version I'm getting a crash at launch and I can't figure out how to debug it.
Stack trace at the bottom of the email.
- The crash does *not* occur
