- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Error Subscript 1 range error impossible to solve ...
Operating System - OpenVMS
1754300
Members
2803
Online
108813
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-04-2009 10:30 PM
тАО10-04-2009 10:30 PM
Re: Error Subscript 1 range error impossible to solve (Alpha VMS 6.2)
Volker,
It's exact :
DBG> EXA 10002C+8
CAL_BIL_COW\I: 0000000A
and
DBG> EXA 10002C+2C
CAL_BIL_COW\COWP: 00000004
It's exact :
DBG> EXA 10002C+8
CAL_BIL_COW\I: 0000000A
and
DBG> EXA 10002C+2C
CAL_BIL_COW\COWP: 00000004
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2009 11:42 PM
тАО10-04-2009 11:42 PM
Re: Error Subscript 1 range error impossible to solve (Alpha VMS 6.2)
Stephane,
how about
DBG> EXA 10002C+30 ! should be AUTRE_COWP
In general one needs to either check the source code, if any subscript of any array could have exceeded the allocation size of the array. Or one needs to analyze the machine code (ideally the complete instruction stream from the .DMP file itself !) to find out, if there are any execution passes leading to L$5 with the correct values of the registers as seen in the dump. Until now, I have not found such a code path, but I'm checking against the machine code listing and not against the actual machine code inside the .DMP file !
Volker.
how about
DBG> EXA 10002C+30 ! should be AUTRE_COWP
In general one needs to either check the source code, if any subscript of any array could have exceeded the allocation size of the array. Or one needs to analyze the machine code (ideally the complete instruction stream from the .DMP file itself !) to find out, if there are any execution passes leading to L$5 with the correct values of the registers as seen in the dump. Until now, I have not found such a code path, but I'm checking against the machine code listing and not against the actual machine code inside the .DMP file !
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 12:46 AM
тАО10-12-2009 12:46 AM
Re: Error Subscript 1 range error impossible to solve (Alpha VMS 6.2)
>Volker: Or one needs to analyze the machine code
If range checking was implemented without much concern for performance, you wouldn't need to look at the machine code. The error message should tell you the name of the variable, index, bounds, file and line number.
I believe the +check= option on HP-UX does this.
If range checking was implemented without much concern for performance, you wouldn't need to look at the machine code. The error message should tell you the name of the variable, index, bounds, file and line number.
I believe the +check= option on HP-UX does this.
- « Previous
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP