From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <00c901c50fa1$ee3ec6d0$88667d50@kilgore> From: "boyd, rounin" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> References: Subject: Re: [9fans] off-topic linux threading bug complaint Date: Thu, 10 Feb 2005 19:54:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 450120f4-eace-11e9-9e20-41e7f4b1d025 > On the other hand, if I guess the process/thread id of the > second pthread, then I can still look at that: > > $ gdb a.out 4724 ahh, when i was doing some driver hacking for some PCI based Xilinx FPGA driver i had to learn a buncha stuff about the process structure and all sorts of horrible mire. from what you describe, it is consistant with the way linux does threads. lunix threads are 'processes' and the thread is therefore a new 'process'. my other guess is that their tools are not in sync with the kernel. does linux have crash(8)? that might shed some more light. -- MGRS 31U DQ 52572 12604