From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19551 invoked by alias); 3 Mar 2008 18:42:26 -0000 Received: (qmail 19542 invoked by uid 22791); 3 Mar 2008 18:42:26 -0000 X-Spam-Check-By: sourceware.org Received: from wall.danger.com (HELO mx.danger.com) (216.220.212.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Mar 2008 18:42:03 +0000 Received: from danger.com (exchange3.danger.com [10.0.1.7]) by mx.danger.com (Postfix) with ESMTP id 6EF053FF8FF for ; Mon, 3 Mar 2008 10:41:56 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Why does gdb use its own thread ids internally rather than the tid from the underlying thread implementation? Date: Mon, 03 Mar 2008 18:42:00 -0000 Message-ID: From: "Martin Fouts" To: Cc: "Mike Chen" X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00023.txt.bz2 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