• 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: Thread ID in crash log
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thread ID in crash log


  • Subject: Re: Thread ID in crash log
  • From: radj <email@hidden>
  • Date: Thu, 18 Dec 2008 14:43:51 +0800

> I've done it that way when debugging threads. It doesn't take long; none of
> the calls take very long,

But there's still a difference, right? And when called or passed through
alot, that small difference can become really big.


> especially when compared to what goes on when
> writing to a log anyway.
>
Yeah, on top of the file locking, there's the slow IO.

The fwrite was just an example. We actually do our debugging through memory
first (ofcourse, there's still locking) and then another debugger thread
does the writing so the real application threads do not have to block on the
IO.
_______________________________________________

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

  • Follow-Ups:
    • Re: Thread ID in crash log
      • From: Scott Ribe <email@hidden>
References: 
 >Re: Thread ID in crash log (From: radj <email@hidden>)
 >Re: Thread ID in crash log (From: Scott Ribe <email@hidden>)

  • Prev by Date: Core Animation glitch
  • Next by Date: Override a UTI?
  • Previous by thread: Re: Thread ID in crash log
  • Next by thread: Re: Thread ID in crash log
  • Index(es):
    • Date
    • Thread