From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4982 invoked by alias); 14 Jun 2004 23:17:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4954 invoked from network); 14 Jun 2004 23:17:51 -0000 Received: from unknown (HELO e35.co.us.ibm.com) (32.97.110.133) by sourceware.org with SMTP; 14 Jun 2004 23:17:51 -0000 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e35.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i5ENHoqF488312 for ; Mon, 14 Jun 2004 19:17:50 -0400 Received: from d03nm113.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i5ENHnC8196152 for ; Mon, 14 Jun 2004 17:17:49 -0600 To: gdb@sources.redhat.com MIME-Version: 1.0 Subject: Did the fix for recycled thread ids uncover another bug? Message-ID: From: Paul Gilliam Date: Mon, 14 Jun 2004 23:17:00 -0000 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2004-06/txt/msg00146.txt.bz2 If I set a breakpoint in a thread function, then when that breakpoint is hit, things go bad. If instead of a breakpoint, I hit cntl-c while the thread function is active, things work right. I have seen this on Intel and ppc. (The Intel was recent, but not current. The ppc was current). The strange thing is that the bug shows up on 32-bit ppc, but not 64-bit ppc. I will post a follow-up with the details if someone tells me this is the right mail-list. -=# Paul Gilliam #=-