diff options
| -rw-r--r-- | gdb/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/PROBLEMS | 17 |
2 files changed, 22 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 34a331a..8d41b7b 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2004-07-26 Michael Chastain <mec.gnu@mindspring.com> + + Document PR threads/1650. + * PROBLEMS (Threads): Document problem with many threads + 2004-07-26 Andrew Cagney <cagney@gnu.org> * gdb-mi.el: Move from here ... diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index 1fa3538..d166305 100644 --- a/gdb/PROBLEMS +++ b/gdb/PROBLEMS @@ -121,3 +121,20 @@ gdb/1505: [regression] gdb prints a bad backtrace for a thread When backtracing a thread, gdb does not stop when it reaches the outermost frame, instead continuing until it hits garbage. This is sensitive to the operating system and thread library. + +*** 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. |