Re: Source file paths showing up in strings of executable
Re: Source file paths showing up in strings of executable
- Subject: Re: Source file paths showing up in strings of executable
- From: Kyle Sluder <email@hidden>
- Date: Tue, 20 Jul 2010 22:17:18 -0700
On Jul 20, 2010, at 10:05 PM, Daniel DeCovnick <email@hidden> wrote:
> Not sure if this is the right list, but since it seems to be exclusive to Obj-C, I'm sending it here.
Questions about Objective-C, and not about the Cocoa APIs specifically, is more on-topic on the objc-language list.
>
> Recently I've noticed that running the command line program "strings" against a release build (with debugging or all symbols stripped) reveals several full paths of source code files, specifically .m and .mm files; I haven't seen .cpp or .c files show up. Strangely, it's not all of them, nor can I find any commonality between them. At one point I thought it was from use of a macro we use around NSLog, but some files using it don't show up, and some which don't use it do. I looked for these files in the .pbxproj, but didn't see anything unusual.
>
> Running strings on other programs showed that other developers, including Apple, have this issue. I looked at Terminal, Xcode, Interface Builder, and Twitterrific, and all had 1-5 source file paths. We have a lot more than that though, around 20.
>
> Does anyone know what causes this, and/or how to prevent it?
Are you remembering to strip debug symbols?
--Kyle Sluder_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden