From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2206 invoked by alias); 26 Jul 2004 15:48:31 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2186 invoked from network); 26 Jul 2004 15:48:30 -0000 Received: from unknown (HELO mclean.mail.mindspring.net) (207.69.200.57) by sourceware.org with SMTP; 26 Jul 2004 15:48:30 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bp7iH-0000V8-00; Mon, 26 Jul 2004 11:48:29 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 4E0E44B104; Mon, 26 Jul 2004 11:48:38 -0400 (EDT) To: eliz@gnu.org Subject: [rfa/PROBLEMS] document threads/1650, thread internal error Cc: gdb-patches@sources.redhat.com Message-Id: <20040726154838.4E0E44B104@berman.michael-chastain.com> Date: Mon, 26 Jul 2004 15:48:00 -0000 From: mec.gnu@mindspring.com (Michael Chastain) X-SW-Source: 2004-07/txt/msg00363.txt.bz2 Here is a PROBLEMS entry for gdb/1650, the internal error on gdb.threads/manythreads.exp. Not tested (don't know how to test ascii documentation). The internal error still happens with both gdb HEAD and gdb gdb_6_2-branch. Andrew says that a set of 30 test runs with NPTL worked fine. Okay to apply to gdb HEAD? Okay to apply to gdb gdb_6_2-branch? Michael C 2004-07-26 Michael Chastain Document PR threads/1650. * PROBLEMS (Threads): Document problem with many threads Index: PROBLEMS =================================================================== RCS file: /cvs/src/src/gdb/PROBLEMS,v retrieving revision 1.32 diff -c -3 -p -r1.32 PROBLEMS *** PROBLEMS 18 Jul 2004 22:29:40 -0000 1.32 --- PROBLEMS 26 Jul 2004 15:44:21 -0000 *************** Fortunately, PowerPC architecture suppor *** 129,131 **** --- 129,149 ---- have been updated. People encountering problems should consider downloading a more current snapshot of GDB (http://www.gnu.org/software/gdb/current/). + + *** Threads + + threads/1650: manythreads.exp + + A program which creates many threads which exit very quickly (hundreds + of thousands of threads in the test program) can cause gdb to generate + an internal error. The internal error often looks like: + + lin-lwp.c:744: internal-error: stop_callback: Assertion `lp->status == 0' failed. + A problem internal to GDB has been detected. + further debugging may prove unreliable. + Quit this debugging session? (y or n) + + This has been observed on native i686-pc-linux-gnu with linuxthreads, + the old threading model. With NPTL threads, this internal error has not + been observed. +