| Title: | Digital Ladebug debugger |
| Moderator: | TLE::LUCIA |
| Created: | Fri Feb 28 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 969 |
| Total number of notes: | 3959 |
On a 4.0b java patch system, I received the following message: > jitd Welcome to the Ladebug Debugger Version 4.0-36 ------------------ object file name: /usr/users/kimball/jit/bin/jit Reading symbolic information ...done (ladebug) stop in RuntimeRoutines::ThrowNewClass [#1: stop in void RuntimeRoutines::ThrowNewClass(JavaClass*) ] (ladebug) run bug1 Pthread context initialization failed with status 99. Unable to switch to decthreads mode.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 944.1 | DCETHD::BUTENHOF | Dave Butenhof, DECthreads | Fri May 02 1997 11:20 | 11 | |
I've often seen failures to initially set $threadlevel="decthreads". This may be a result of ladebug trying to get into libpthreaddebug before the target process is fully initialized. Although I'm not entirely sure what (or where) the problem is, I do know that we (DECthreads) handle this much better on PTmin, and I haven't seen these problems in the later code. Usually when I've seen this problem on 4.0B and before, I've been able to manually set $threadlevel="decthreads" after hitting a breakpoint, and it works fine. /dave | |||||
| 944.2 | TLE::BRETT | Fri May 02 1997 13:31 | 3 | ||
This problem seems to happen much more often on a JAVA-patched 4.0B system. /Bevin | |||||