• 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: inline, optimize, and call stack visibility?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: inline, optimize, and call stack visibility?


  • Subject: Re: inline, optimize, and call stack visibility?
  • From: "Sean McBride" <email@hidden>
  • Date: Wed, 26 Jan 2011 11:24:36 -0500
  • Organization: Rogue Research Inc.

On Tue, 25 Jan 2011 15:01:01 -0800, David M. Cotter said:

>In my app, if it crashes on a user, it generates a crash report which
>gets sent to me.
>
>i have a class that's created on different threads
>
>i want to differentiate between each thread, so i can READ which thread
>it is by looking at the call stack

You could us pthread_setname_np() to give each thread a unique name, the
crash reporter uses that name in crash reports.

--
____________________________________________________________
Sean McBride, B. Eng                 email@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada


 _______________________________________________
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: 
 >inline, optimize, and call stack visibility? (From: "David M. Cotter" <email@hidden>)

  • Prev by Date: Re: inline, optimize, and call stack visibility?
  • Next by Date: Leak Detection in Unit Test
  • Previous by thread: Re: inline, optimize, and call stack visibility?
  • Next by thread: Annoying IB bug still not fixed
  • Index(es):
    • Date
    • Thread