Title: | DEBUG |
Notice: | Updated locations for reporting QARs -- see note 834.1 |
Moderator: | LOWFAT::DIETER |
Created: | Fri Jan 24 1986 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1868 |
Total number of notes: | 8200 |
A customer reports that he is not able to connect to his application (connect hangs). If he runs a simple 'sleep() in a loop' program instead, connect works. Any idea what could cause this behaviour ? Version info: OpenVMS Alpha V7.1. regards Wolfgang
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1862.1 | SSPADE::SSPADE::HILDE | Thu May 22 1997 18:35 | 14 | ||
>Any idea what could cause this behaviour? No, too many possiblities. Can you get any more details...perhaps even a reproducer? Is the application single threaded and running on a single CPU machine? Can you look at the system from another window via ANA/SYS and determine the state of the application process and the debugger main process? What flavor of CONNECT is this, connect to an up and running process, connect to spawned process either from the debugger or from an app already under debug control, connect %node for System Code Debugging,...? More details, please. Lon | |||||
1862.2 | VIRRUS::diewald | Vortex of Chaos | Wed May 28 1997 15:36 | 10 | |
A few other thoughts... * Does the program use $HIBER/$WAKE, or any of the system routines that might use them? * Does the program do anything to change any exception handlers? Just having a flashback... Jeff Diewald Ladebug team |