[Lldb-commits] [PATCH] Add Host::GetMaxThreadNameLength(), modify private state thread name

Todd Fiala tfiala at google.com
Sat Jul 12 15:21:31 PDT 2014

Well, we can keep it simple until proven needed to be more complex :-)
 I'll switch it to a constant and re-send.

On Saturday, July 12, 2014, Ed Maste <emaste at freebsd.org> wrote:

> On 11 July 2014 11:56, Todd Fiala <todd.fiala at gmail.com <javascript:;>>
> wrote:
> > My take was it depends on host details.  For example, I didn't track down
> > the Windows way of getting this data, but I wouldn't be surprised if it
> > turned into a method call to the system (which could be cached, but
> that's
> > an impl detail that a method call would allow us to hide).
> >
> > I thought it made it more flexible on unknown details for current/future
> > platforms to have it be a function call.
> Fair enough, and it's not a big deal - I just assume it will in
> general be a (possibly empirically determined) constant.
> I did a little digging and couldn't find a limit for Windows.  I did
> discover the convoluted method used to set the thread name though:
> http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at cs.uiuc.edu <javascript:;>
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits

Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20140712/95766f8a/attachment.html>

More information about the lldb-commits mailing list