From 537e1b88f8c33deec40bc9eaada8a41ee62478c3 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Wed, 28 Jul 2004 19:53:39 +0000 Subject: 2004-07-28 Andrew Cagney * PROBLEMS: Mention threads/1650. * NEWS: Mention the NPTL fix. --- gdb/PROBLEMS | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) (limited to 'gdb/PROBLEMS') diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index d166305722b..8cdfe324756 100644 --- a/gdb/PROBLEMS +++ b/gdb/PROBLEMS @@ -126,15 +126,9 @@ sensitive to the operating system and thread library. 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. +On GNU/Linux systems that use the old LinuxThreads thread library, a +program rapidly creating and deleting threads can confuse GDB leading +to an internal error. + +This problem does not occur on newer systems that use the NPTL +library, and did not occur with GDB 6.1. -- cgit v1.2.1