• 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_t, uthread_t, at al.?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: thread_t, uthread_t, at al.?


  • Subject: Re: thread_t, uthread_t, at al.?
  • From: plumber Idraulico <email@hidden>
  • Date: Fri, 27 Oct 2006 18:39:04 +0200

Hi Shawn,
i don't think there is a problem,
the "question" can be considered differently,

i don't think that we can speak about enhancement
it's a "different point of view" mechanism

but it 's only my humble opinion.

Peace

-plum

> On Oct 27, 2006, at 1:50 AM, Rick Mann wrote:
>
> I don't believe that there is KPI to easily do what you're asking.
> Why do you want to know the PID associated with an arbitrary
> thread?  Is it not something you can obtain while you are being run
> on that thread?
>
>  = Mike

Hi, Mike
this approach exists on other nix* like Linux , Solaris ....


What problem is it solving? What is the use case for it.

Answer those types of question and use that information to file an
enhancement report with Apple.

-Shawn

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >thread_t, uthread_t, at al.? (From: Rick Mann <email@hidden>)
 >Re: thread_t, uthread_t, at al.? (From: Michael Smith <email@hidden>)
 >Re: thread_t, uthread_t, at al.? (From: plumber Idraulico <email@hidden>)
 >Re: Re: thread_t, uthread_t, at al.? (From: "Shawn Erickson" <email@hidden>)

  • Prev by Date: Re: thread_t, uthread_t, at al.?
  • Next by Date: Re: thread_t, uthread_t, at al.?
  • Previous by thread: Re: Re: thread_t, uthread_t, at al.?
  • Next by thread: Re: thread_t, uthread_t, at al.?
  • Index(es):
    • Date
    • Thread