• 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: Universal Binary Crash Logs With Bogus Line Numbers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Universal Binary Crash Logs With Bogus Line Numbers


  • Subject: Re: Universal Binary Crash Logs With Bogus Line Numbers
  • From: David Alger <email@hidden>
  • Date: Mon, 19 Jun 2006 19:48:02 -0500

In my haste I my some sad mistakes. :-)

This is what my post should read.


Greetings,

Why when my universal binary crashes in one of my files, does it give me bogus line numbers that don't exist?
Before I made it universal the line numbers I got all seemed to be fine.


For example, I have a file with just a few functions in it. The file is just under 200 lines, but in a crash I was getting it showed that code was executing in a function located in that file, but on a line number in the whereabouts of 2500 range.

Is there something special I need to do to translate the line numbers or something?

Mac OS X: 10.4.6
Xcode: 2.3

2Ghz Intel MacBook

TIA,
David Alger

Family Friendly Software, LLC
http://www.familyfriendlysoftware.com
_______________________________________________
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: 
 >Universal Binary Crash Logs With Bogus Line Numbers (From: David Alger <email@hidden>)

  • Prev by Date: Universal Binary Crash Logs With Bogus Line Numbers
  • Next by Date: Re: Project Assistant renames home folder without authorisation Re: define GCC_PREFIX_FILE setting at project level?
  • Previous by thread: Universal Binary Crash Logs With Bogus Line Numbers
  • Next by thread: shell script from finder
  • Index(es):
    • Date
    • Thread