• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dead code stripping and crash logs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dead code stripping and crash logs


  • Subject: Re: Dead code stripping and crash logs
  • From: Eric Albert <email@hidden>
  • Date: Mon, 12 Dec 2005 07:42:38 -0800

On Dec 12, 2005, at 3:18 AM, Jerry wrote:

If we build our app with dead code stripping turned on, then if the app crashes for some reason, instead of the user seeing the "Unexpectedly Quit" alert, the app just hangs. This is really annoying for the user and for us because we can't get a crash log to determine what happened. While the app is hung, there's no way to get a stack trace - gdb, Shark, Sampler etc. all fail to retrieve the stack.

Has anyone else seen this problem, and have a workround perhaps?

I've never seen that or heard of anything quite like it. Can you file a bug report and attach a copy of your application? We don't need the source code; just the built binary that reproduces this problem. For that matter, it'd be nice to have a version built without dead code stripping, too.


Thanks,
Eric

_______________________________________________
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


References: 
 >Dead code stripping and crash logs (From: Jerry <email@hidden>)

  • Prev by Date: Build pane is broken, when using All-In-One mode
  • Next by Date: Re: Build pane is broken, when using All-In-One mode
  • Previous by thread: Dead code stripping and crash logs
  • Next by thread: Build pane is broken, when using All-In-One mode
  • Index(es):
    • Date
    • Thread