Re: weird message in gdb
Re: weird message in gdb
- Subject: Re: weird message in gdb
- From: Jim Ingham <email@hidden>
- Date: Fri, 16 Sep 2011 11:05:34 -0700
On MacOS X the totality of the debug information is not copied into the resultant binary, but left in the .o files and the only debug info in the binary is the list of source files and paths to associated .o files. If you want to keep the debug information long term, you make a dSYM file (Xcode does this by default for the release configuration.) But if you're going to ship a library, you also should strip the debug information with "strip -S", since all it does is tell the debugger about .o files your users don't have... Again, Xcode does this by default for release configurations. But if somebody did ship a library with this debug information still in it, you can run "strip -S" on it yourself. All this does is remove debug information, so it won't affect the usefulness of the library, and that way you won't get these messages anymore.
Jim
On Sep 16, 2011, at 8:00 AM, Bayes Scott F wrote:
> Hi Jens,
>
>> That path must be the original path to the source file on the machine that plugin was compiled on. The compiler leaves such paths in the object code to help debuggers locate the source code later on.
>
> Yes, that was my thought too. Tried strings on everything I saw inside the bundle, but didn't find it. It wasn't an organized search however, and I probably missed a file or two. Compiler/linker leaves it in on purpose: interesting.
>
> But it does generate the warning in gdb, which seems to indicate some (small) problem that a fresh download didn't fix, so I zipped the picker for now, so as not to have the messages.
>
> I'm a bit (more than before) disappointed in Spotlight, not searching everywhere when you think you've told it to.
>
> Many thanks to all,
>
>
> Scott
>
> On Sep 15, 2011, at 22:56, Jens Alfke wrote:
>
>>
>> On Sep 15, 2011, at 10:50 PM, Scott F Bayes wrote:
>>
>>> Funny, I did a Spotlight content search for "BlackOps" with System Files included, but it didn't show up. Was thinking about xargs and find and other stuff but I'm real rusty on sh/ksh/bash.
>>
>> Spotlight won’t search inside executable machine code. There are strings to be found there, but you’ll need more specialized (or more general) tools to find them.
>>
>> That path must be the original path to the source file on the machine that plugin was compiled on. The compiler leaves such paths in the object code to help debuggers locate the source code later on.
>>
>> —Jens
>
> _______________________________________________
> 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
_______________________________________________
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