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: Mon, 17 Nov 2003 09:10:58 -0800
Philip,
It's a little hard to tell what is going on with that little of the
backtrace. But the immediate cause is that whenever dyld has a problem
resolving symbols while loading your application, it signals the error
by calling the same trap instruction that gdb uses to set breakpoints.
Thus you will stop in the debugger at the point where the error
occurred if you are running in the debugger.
So the thing we have to determine is what is causing dyld not to be
able to look up the symbols. Most likely it is something in the
environment that is different between running under command line gdb,
and under Xcode. You can compare these pretty easily. In Xcode, open
the gdb console window and type
(gdb) show env
do the same when running under command-line gdb and see if anything
suspicious shows up.
There is also an environment variable that you can set to help debug
dyld problems. Setting DYLD_PRINT_LIBRARIES to 1 will dump a printout
of all the libraries as they are being loaded to stdout. Presumably
the last one in the list will be what is causing the problem.
If you don't see anything obvious, feel free to send along the results
of show env for both environments, and the DYLD_PRINT_LIBRARIES output,
and we will see if we can see anything.
Jim
On Nov 16, 2003, at 12:43 AM, Philip Mvtteli wrote:
Hi
I have a foundation tool and an application. Both of these
applications run perfectly stand-alone and in the debugger (gdb)
from the command line.
But when I want to debug in Xcode, the dyld seems to stop and I have
the following backtrace:
(gdb) bt
#0 0x00003210 in dyld_func_lookup_pointer ()
#1 0x00003208 in dyld_func_lookup_pointer ()
Am 15.11.2003 um 21:31 schrieb chris friesen:
Your cached sym files (for gdb) need to be regenerated. You need to
run the following at the command line:
sudo /usr/libexec/gdb/cache-symfiles
Very unfortunately, this didn't change anything. I even removed the
sym folder completely, so I had no messages about sym files
out-of-date anymore. But still, the debugger in Xcode stopps at the
very same place, during the debugger, started from the Terminal, runs
the program without the slightest problem.
Thanks
Phil
_______________________________________________
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.
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham
email@hidden
Developer Tools - gdb
_______________________________________________
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.