-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.