From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2974 invoked by alias); 26 Jul 2004 19:51:28 -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 2966 invoked from network); 26 Jul 2004 19:51:27 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 26 Jul 2004 19:51:27 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i6QJpRe3011162 for ; Mon, 26 Jul 2004 15:51:27 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i6QJpLa32129; Mon, 26 Jul 2004 15:51:21 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 971712B9D; Mon, 26 Jul 2004 15:51:16 -0400 (EDT) Message-ID: <410560B4.70207@gnu.org> Date: Mon, 26 Jul 2004 19:51:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Michael Chastain Cc: eliz@gnu.org, gdb-patches@sources.redhat.com Subject: Re: [rfa/PROBLEMS] document threads/1650, thread internal error References: <20040726154838.4E0E44B104@berman.michael-chastain.com> In-Reply-To: <20040726154838.4E0E44B104@berman.michael-chastain.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00377.txt.bz2 > + > + *** 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. > + I think it more clearly needs to convey the following information: - that it is (to the best of our knowledge) GNU/Linux and LinuxThreads specific So the opening sentence should mention both of those data points. Something like ``On a GNU/Linux system that uses linuxthreads, a program ....'' - switching to NPTL highly recommended So the closing paragraph should make this clearer. Something like ``This problem has not been observed on GNU/Linux systems that use NPTL (New Posix Threads Library[?]). People still using linuxthreads are strongly encouraged to migrate to NPTL''. We should also mention that on GNU/Linux NPTL based systems a problem with GDB loosing track of threads was fixed. Andrew