- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: OpenVMS stack traceback
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
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
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
10-14-2011 03:02 AM
10-14-2011 03:02 AM
I'm having a bit of trouble with the OpenVMS stack traceback facility (the facility whereby when a process crashes, sys$output contains a printout starting with %TRACE_F_TRACEBACK, showing an unwind of the stack). It appears that if the crashing process is a detached process, the traceback is produced only if 'set message /facility' was in force when the process was created. If I enter 'set message /nofacility' before creating the detached process, then when the detached process crashes, no traceback is produced. This doesn't seem to apply to non-detached processes. I haven't found any reference to this behaviour in the OpenVMS manuals. So, I have two questions:
(a) Have I totally got the wrong end of the stick here, or is this really true and it's supposed to be like this?
(b) Is there a way of doing 'set message /facility' using a system service? If so, my detached processes could do that immediately after they start up, to make sure there will be a traceback if they crash.
This is OpenVMS 8.3-1H1 running on an rx2660, using the HP C compiler version 7.1. The detached processes are created by a command file using loginout.exe, like this:
$ run sys$system:loginout.exe -
/detach -
/page_file=500000 -
/process_name=xyz -
/priority=nn -
/input=runxyz.com -
/output=xyz.out
'runxyz.com' looks like this:
$ define /table=lnm$process_directory lnm$temporary_mailbox lnm$group
$ run xyz.exe
Thanks in advance... Max.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 04:31 AM
10-14-2011 04:31 AM
Re: OpenVMS stack traceback
>>> (a) Have I totally got the wrong end of the stick here, or is this really true and it's supposed to be like this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:21 AM
10-14-2011 05:21 AM
Re: OpenVMS stack traceback
Yes, I've already tried putting 'set message /facility' in runxyz.com, and that does fix the problem. Thanks.
I've been playing round with it a bit more and it seems that for a detached process, setting any one of the message parameters /facility, /text, /identification and /severity ensures you get a traceback on a crash. But if all four of them are off, you get no traceback. This looks as if it could be deliberate, but doesn't seem to be mentioned in the manuals.
I've noticed that Eli M Barasch posted a similar problem (lack of traceback when detached processes crash) in September 2010, and nobody seems to have mentioned 'set message' in their reply. Maybe this was his problem too?
As for my crashes: I don't have any crashes to worry about at the moment. This is about ensuring that I will get a traceback if crashes occur in the future. I'm testing with a deliberate ACCVIO crash caused by this code in a detached process:
char *p = "JJJ";
*p = 0;
Thanks for the help...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:27 AM
10-14-2011 05:27 AM
Re: OpenVMS stack traceback
Max,
by default, all the message parameters are enabled, aren't they ? Why not in your process ? Do you have some login procedure, which turns them off ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:33 AM
10-14-2011 05:33 AM
Re: OpenVMS stack traceback
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:37 AM
10-14-2011 05:37 AM
Re: OpenVMS stack traceback
Max,
that may explain, why Hartmut couldn't reproduce your problem...
This may therefore be a behaviour triggered by an unusual local system configuration.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:38 AM - edited 10-14-2011 05:40 AM
10-14-2011 05:38 AM - edited 10-14-2011 05:40 AM
SolutionAdd the /DUMP qualifier to the RUN command (for non-LOGINOUT processes) and add the /DUMP switch onto the individual image invocations when started at DCL), and catch your errors using the process dump mechanisms and the OpenVMS debugger. (qv: ANALYZE /PROCESS_DUMP, etc)
Or better, add your own signal handler and your own process-dump handing code into the application, and log the stuff that matters to your application, should it tip over.
(Not sure where a reply I'd thought was posted here went, either.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 05:54 AM
10-14-2011 05:54 AM
Re: OpenVMS stack traceback
>>> But if all four of them are off, you get no traceback. This looks as if it could be deliberate, but doesn't seem to be mentioned in the manuals.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 09:22 AM
10-14-2011 09:22 AM
Re: OpenVMS stack traceback
Yes, I think you may be right. In any case I now know enough to do what I need... thanks to all for your help... Max.