This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Why does gdb use its own thread ids internally rather than the tid from the underlying thread implementation?


Hi,

We're trying to optimize the NetBSD 4.0 implementation of pthreads,
which has an M:N thread implementation, and are having some trouble
getting gdb to work because the underlying thread id for a thread can
change in an M:N implementation.

Can anyone provide any insight into why gdb doesn't use the underlying
thread id?

Or suggestions about how to accommodate M:N without zombie queues?

Thanks,

Marty


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]