- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Debugger Question
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 03:22 AM
тАО11-12-2009 03:22 AM
Debugger Question
small reproducer (fortran):
program testit
implicit none
integer*4 i
integer*4 j
i = 3
j = 4
end
program testit2
implicit none
integer*4 i
integer*4 j
i = 3
j = 4
end
fortr/debu/noop testit
fortr/debu/noop testit2
link/debu testit
link/debu testit2
run testit
dbg> step
dbg> spawn
$ run testit 2
Under OpenVMS 7.3 this works, I get the debugger version (OpenVMS Alpha Debug64 Version V7.2X-022) and the debug prompt.
Under openVMS 7.3-2 (debug version OpenVMS Alpha Debug64 Version V7.3-200) there is no prompt. Main session is HIB, dbg$xxxx and subprocess are in LEF.
It is not possible to patch the debugger because these patches introduce bugs concerning examine/deposit fortran record elements.
What has changed ?
Is there a workaround ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 04:36 AM
тАО11-12-2009 04:36 AM
Re: Debugger Question
Did you try set the job logical DBG$PROCESS to
MULTIPROCESS ?
$ HELP/LIBRARY=SYS$HELP:DBG$HELP DEBUG Logical_Names DBG$PROCESS
:
" Use the multiprocess configuration to debug programs that normally run in more than one process."
:
For more information, see help on Debugging_Configurations.
:
hth,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 04:46 AM
тАО11-12-2009 04:46 AM
Re: Debugger Question
until this moment I didn't try this. But now I tried this first:
$ HELP/LIBRARY=SYS$HELP:DBG$HELP DEBUG Logical_Names DBG$PROCESS
DEBUG
Logical_Names
Sorry, no documentation on DEBUG LOGICAL_NAMES DBG$PROCESS
I became curious and tried it with 8.3
Help ... did work
but the problem with the debugger persists. Even worse: I had to stop/id=nnn my session because ctl-Y didn't work.
It (ctl-Y) worked with 7.3-2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 05:26 AM
тАО11-12-2009 05:26 AM
Re: Debugger Question
Along the lines of "what problem are you really trying to solve", may we assume that the processesing to be tested must have a parent - subprocess relationship?
Can you work around that, punt the issue by performing the test simply using two debug sessions? That would seem a lot easier on th whole!
To figure out what is going on, you may need to check the status of the various processes involved, and notably what they are waiting for. ANAL/SYS ... SHOW PROC/CHAN ... look for 'busy' can be a handy way to see mailbox IO.
Maybe you are low on process resources? (bytlm, tqe,...).
Does $ SHOW PROC/CONT on 7.3-2 have the 'q' page?
Probably not... find a command file to list quotas and usage?
Something wrong with Pthreads?
Just guesses.
Good luck!
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 06:11 AM
тАО11-12-2009 06:11 AM
Re: Debugger Question
The alternative (and the approach I usually use) redirects the debugger session and debugger output from the detached processes (or your subprocess, here) to another terminal.
http://labs.hoffmanlabs.com/node/803
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 06:28 AM
тАО11-12-2009 06:28 AM
Re: Debugger Question
the software to test has a parent-subprocess relationship. Testing the real programs in two different sessions would not be the same.
For my primitive reproducer there are three processes involved:
main process - state HIB
dbg$xxxx - state LEF
subprocess spawned from within the debugger - state LEF
None of the processes seems to have problems with quotas.
ANA/SYS -> SHO PROC/CHAN ... shows no busy i/o channel, again none of the processes involved has any busy i/o channel !!!
SHOW PROC does not have the q page on 7.3-2 but ana/sys ... SHOW PROC helps.
On 8.3 there are no problems with quota (q page available).
What do you try to tell me about PThreads ?
We don't use it explicitly.
Hoff,
my original post contains a small reproducer, nearly as simple as I can imagine.
I also tried to redirect debugger input and output (DBG$INPUT and DBG$OUTPUT) to another terminal, btw. that's the way I use to work, too. But it does not work. I also tried to redirect debug input/output to different terminals (one for the main process, the other one for the subprocess). Always the same result: debugging not possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 06:34 AM
тАО11-12-2009 06:34 AM
Re: Debugger Question
If forcing the single-process debugger or raising the debug session via DECwindows doesn't work, then you'll probably end up starting another session.
Looks like the debugger is getting itself tangled.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2009 06:39 AM
тАО11-12-2009 06:39 AM
Re: Debugger Question
yes, that's what it looks like.
A new 'feature' introduced with 7.3-2
and updated with 8.3 to force user to kill their processes.