Re: [SOLVED] Debugging ARC app on Snow Leopard
Re: [SOLVED] Debugging ARC app on Snow Leopard
- Subject: Re: [SOLVED] Debugging ARC app on Snow Leopard
- From: Dave Fernandes <email@hidden>
- Date: Mon, 28 Nov 2011 18:28:18 -0500
On 2011-11-28, at 3:47 PM, Chris Cleeland wrote:
> On Mon, Nov 28, 2011 at 2:03 PM, Dave Fernandes
> <email@hidden> wrote:
>>
>> I'll file a bug report on Xcode - that it should use relative paths for the object files.
>
> Typically this is a debugger issue, not a compiler issue. Every other
> platform I've used stores the full paths in debug info, too.
Yes, it looks like this behavior is expected:
"Changes since Xcode 2.2 Developer tools update (gdb-437)
• Support for DWARF debug file format
GDB now supports the use of the DWARF debug file format. It can work with DWARF in one of two ways: The debug information is stored primarily in the .o object files with a little bit in the executable, and with all of the debug information collected into a dSYM file and no debug information in the executable.
For normal change-compile-debug, change-compile-debug workflow, leaving the debug information in the .o files is the intended usage. A dSYM file should be created when you are distributing your binary to another person who will need to debug it, or archiving the debug information of a release binary so you can debug crash reports/bugs that are reported to you later.
In the case of debug information in .o files, the .o files must remain in their original location for gdb to find them. They may be copied to another system, but the pathname must remain the same -- or soft symbolic links (cf ln(1)) must be put in place."
_______________________________________________
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