Just FYI,
Windows' way to have the program affect thread names in the
debugger is with SetThreadName, which throws a magic exception
which the debugger can catch. GDB doesn't know about this though.
http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx
Just for completeness... I don't know if
On Feb 24 05:00, Yaakov (Cygwin/X) wrote:
> On Fri, 2012-02-24 at 10:38 +0100, Corinna Vinschen wrote:
> > On Feb 23 21:38, Yaakov (Cygwin/X) wrote:
> > > This patchset adds pthread_getname_np and pthread_setname_np. These
> > > were added to glibc in 2.12[1] and are also present in some form on
>
On Fri, 2012-02-24 at 10:38 +0100, Corinna Vinschen wrote:
> On Feb 23 21:38, Yaakov (Cygwin/X) wrote:
> > This patchset adds pthread_getname_np and pthread_setname_np. These
> > were added to glibc in 2.12[1] and are also present in some form on
> > NetBSD and several UNIXes. IIUC recent version
On Feb 23 21:38, Yaakov (Cygwin/X) wrote:
> This patchset adds pthread_getname_np and pthread_setname_np. These
> were added to glibc in 2.12[1] and are also present in some form on
> NetBSD and several UNIXes. IIUC recent versions of GDB can benefit from
> this support.
Thanks for your patch, b