• 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
Resolving crash line in expanded macro
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Resolving crash line in expanded macro


  • Subject: Resolving crash line in expanded macro
  • From: Markus Spoettl <email@hidden>
  • Date: Tue, 29 Apr 2014 16:03:47 +0200

Hi,

  I have a symbolicated crash log from a release version of my app.

The problem is that the last line in the call stack before the actual crash (so the second from the top) is a macro "call" that expands into other macros which eventually expand into A LOT of code (more than 500 lines). Is there a way to find out what line in the preprocessed source file caused this?

If that's not possible without preparation, is there a way to compile with debug info that will allow me to track down the culprit the next time this happens?

Thanks for any pointers!

Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
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


  • Prev by Date: Re: Xcode 3.2.6 file names and lion
  • Next by Date: Filemerge questions
  • Previous by thread: Re: Xcode 3.2.6 file names and lion
  • Next by thread: Filemerge questions
  • Index(es):
    • Date
    • Thread