Re: Why does Xcode's GDB Stop in "dyld_func_lookup_pointer"?
Re: Why does Xcode's GDB Stop in "dyld_func_lookup_pointer"?
- Subject: Re: Why does Xcode's GDB Stop in "dyld_func_lookup_pointer"?
- From: Jim Ingham <email@hidden>
- Date: Fri, 21 Nov 2003 10:20:25 -0800
Philip,
I can't see anything immediately wrong here. I noted below what some
of these do. See "man dyld" for more details. The best way to proceed
is to run command-line gdb, but set each of these variables one by one
in gdb before you load your executable, like:
$ gdb
...
(gdb) set env DYLD_LIBRARY_PATH /tmp
(gdb) file <Path to executable>
(gdb) run
etc, and see which one causes gdb to fall over. Xcode runs gdb pretty
much the same way you would from the console, or DDD would. So it
pretty much has to be something that is set in the environment that is
causing the problem...
On Nov 20, 2003, at 3:13 AM, Philip Mvtteli wrote:
Here's the environment for Xcode:
SHELL=/bin/zsh
USER=moetteli
SSH_AUTH_SOCK=/tmp/500/nl.uu.phil.SSHAgent.socket
__CF_USER_TEXT_ENCODING=0x1F4:0:19
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/Users/moetteli
PWD=/private/tmp
SHLVL=0
HOME=/Users/moetteli
DISPLAY=:0.0
SECURITYSESSIONID=20fd70
DYLD_IMAGE_SUFFIX=_debug
You are passing this because you turned the "Dynamic Library Runtime
Variant" popup in the Executable editor to debug. Setting this causes
dyld to load the _debug variants of all the shared libraries on the
system if they exist. Maybe one of the debug variants is mangled
somehow? Anyway, try turning this to Standard, and see if that helps.
The debug variant of the library generally has nothing to do with
debugging as in debug symbols... It generally means you run with
versions of the system libraries that have lots of internal asserts &
warnings are turned on. You don't need this for debugging generally.
DYLD_INSERT_LIBRARIES=/Developer/Applications/Xcode.app/Contents/
PlugIns/GDBMIDebugging.pbplugin/Contents/Resources/
PBGDBIntrospectionSupport.A.dylib
NSUnbufferedIO=YES
DYLD_PRINT_LIBRARIES=1
DYLD_LIBRARY_PATH=/tmp
DYLD_FRAMEWORK_PATH=/tmp
This adds /tmp to the library search path (the Mac OS X equivalent of
LD_LIBRARY_PATH if you are familiar with that.) Is there anything
suspicious in /tmp that this might be picking up???
DYLD_NEW_LOCAL_SHARED_REGIONS=YES
DYLD_NO_FIX_PREBINDING=YES
--
Jim Ingham email@hidden
Developer Tools
Apple Computer
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.