diff options
| author | Michael Chastain <mec@google.com> | 2004-07-27 00:01:17 +0000 |
|---|---|---|
| committer | Michael Chastain <mec@google.com> | 2004-07-27 00:01:17 +0000 |
| commit | 536517dd94c3cca243eb247854e2b712053dd730 (patch) | |
| tree | 01dec80f2e4a2d75e125d39b011f071d6d484238 /gdb/PROBLEMS | |
| parent | df66ddfe36ab4535066efd233fc03320470019aa (diff) | |
| download | gdb-536517dd94c3cca243eb247854e2b712053dd730.zip gdb-536517dd94c3cca243eb247854e2b712053dd730.tar.gz gdb-536517dd94c3cca243eb247854e2b712053dd730.tar.bz2 | |
2004-07-26 Michael Chastain <mec.gnu@mindspring.com>
Document PR threads/1650.
* PROBLEMS (Threads): Document problem with many threads
Diffstat (limited to 'gdb/PROBLEMS')
| -rw-r--r-- | gdb/PROBLEMS | 17 |
1 files changed, 17 insertions, 0 deletions
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. |