- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: PCA memory problems
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
тАО10-14-2004 08:07 PM
тАО10-14-2004 08:07 PM
PCA memory problems
When using the Performance and Coverage Analyser for one of our applications, we get the following error:
%DEBUG-E-INTERR, debugger error in GETMEMORY\DBG$GET_MEMORY memory request too large or session corruption
We watched the quotas while running the application and saw no problems there.
The application has been compiled and linked with /DEBUG.
The application is started with a script like this :
$ define/job lib$debug sys$library:pca$collector.exe
$ define PCAC$DECW$DISPLAY " "
$ define PCAC$INIT STARTUP.PCAC
$ set def SYS$LOGIN
$ @start ! script to start the application
The contents of STARTUP.PCAC :
set datafile/append/executable
set language C
set coverage/previous/anc/stack_pcs program by line
go
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-16-2004 07:56 AM
тАО10-16-2004 07:56 AM
Re: PCA memory problems
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2004 05:24 PM
тАО10-17-2004 05:24 PM
Re: PCA memory problems
VMS version 7.2-1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2004 10:51 PM
тАО10-17-2004 10:51 PM
Re: PCA memory problems
the SET COVERAGE command being used sets a breakpoint for every source line in the program and will use a large amount of memory. Try collecting coverage data module by module instead.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2004 10:55 PM
тАО10-17-2004 10:55 PM
Re: PCA memory problems
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2004 11:02 PM
тАО10-17-2004 11:02 PM
Re: PCA memory problems
Currently there is only the tests for one of the programs are not run because of the PCA error. With the tested programs we do not have this problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2004 06:47 PM
тАО10-21-2004 06:47 PM
Re: PCA memory problems
We now generate the initialisation file STARTUP.PCAC (see original post) with
SET COVERAGE/PREVIOUS/ANC/UNTIL=1 MOD
for each module for which we want to get coverage data (libraries excluded).
To get the data we have to explicitly request the coverage data for a specific module with:
TAB /COVERAGE MOD
We have seen the error only one or two times, when a lot of users were busy and the system load was quite high.
Now we have another question:
In the output all header files are printed, but they contain no coverage information.
It is about 1800 pages of useless information. This is in the output of only one module. The entire output for this module is 2300 pages!!!.
Is there anyway to disable the printing of header files in the output???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2004 01:47 AM
тАО10-25-2004 01:47 AM
Re: PCA memory problems
unfourtunally the debug symbol table that PCA (and the debugger) use contains line numbers for the source after the pre-processor has included all header files. The bad news is that nothing much can be done. The good news is that things are done differently on itanium VMS and its not a problem on that platform.
Purely Personal Opinion