Re: Framework Links Work OK in 10.5 and 10.4, Crash in 10.3
Re: Framework Links Work OK in 10.5 and 10.4, Crash in 10.3
- Subject: Re: Framework Links Work OK in 10.5 and 10.4, Crash in 10.3
- From: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 18 Mar 2008 18:29:23 +0100
Le 18 mars 08 à 17:15, Jerry Krinock a écrit :
After studying the documentation on prebinding [1], I've concluded
that neither my app nor my framework are prebound, and that should
be fine, since the only benefit of prebinding is that the app might
launch a little faster in 10.3. I don't care how long my half-dozen
10.3 users have to wait. Just don't crash and I'll be happy.
I did notice one odd thing. That document states that address range
0xfffe0000 to 0xffffffff is "Reserved for use by system services. Do
not use this address range." Looking back at the crash report in my
original post, I see that the address at the crash, 0xfffeff00, is
near the bottom of this range. Maybe that might give someone who is
smarter than me a clue?
Here is what I get upon otool-ing the framework:
Jerrys-Mac-Mini:A jk$ otool -hv SSLocalize
SSLocalize:
Mach header
magic cputype cpusubtype caps filetype ncmds
sizeofcmds flags
MH_MAGIC I386 ALL 0x00 DYLIB 16 2276
NOUNDEFS DYLDLINK TWOLEVEL NO_REEXPORTED_DYLIBS
Jerry
If this is for 10.3 what about "otool -arch ppc -hv SSLocalize"
instead ;-)
Most of the tool to manipulate binaries on OS X accept the -arch flag.
(nm, otool, etc…)
Prebiding is just an optimization hack and I not sure it is usefull on
10.3.9 (this version include a new dyld).
If you do not force the address of your library (using -image_base
linker flags) the system choose an address to load it and it is
allowed to use reserved space ;-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden