- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- access violation
Operating System - OpenVMS
1820475
Members
3194
Online
109624
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
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
тАО12-17-2008 02:03 AM
тАО12-17-2008 02:03 AM
Hi
Any hints from someone where I should start looking for reason for below access violation?
It is a new program. Does it require some more quota or. What is most common reason for "access violation"?
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0000000000110000, PC=FF
FFFFFF84260D11, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBOTS 0 0000000000012D11 FFFFFFFF84260D11
libclntsh ttcx2y ttcc2u 427560 0000000000002110 000000000135D230
libclntsh ttcx2y ttcs2c 429560 000000000000ED20 0000000001369E40
libclntsh ttcacs ttcacr 415042 0000000000005DD0 00000000013587F0
libclntsh ttcdrv ttcdrv 1433700 0000000000002BC0 000000000139B080
libclntsh nioqwa nioqwa 162140 00000000000000C0 0000000000A62420
libclntsh upiprv upirtrc 418061 0000000000002300 000000000069C200
libclntsh kpurc kpurcsc 396905 00000000000001B0 00000000005A84F0
libclntsh kpuex kpuexecv8 1056507 0000000000009030 00000000004F9920
libclntsh kpuex kpuexec 1057935 000000000000FD50 0000000000500640
libclntsh oci8 OCIStmtExecute #1182 00000000000020F0 0000000000238A50
FBFSSND 0 000000000008FC70 000000000008FC70
FBFSSND 0 0000000000071D80 0000000000071D80
FBFSSND 0 00000000000507F0 00000000000507F0
FBFSSND 0 0000000000051AB0 0000000000051AB0
FBFSSND 0 0000000000052A30 0000000000052A30
FBFSSND 0 0000000000053E20 0000000000053E20
FBFSSND 0 0000000000053F50 0000000000053F50
FBFSSND 0 00000000000BDD00 00000000000BDD00
FBFSSND 0 00000000000CA3B0 00000000000CA3B0
PTHREAD$RTL THD_THREAD thdBase 243309 0000000000005BF0 FFFFFFFF84541440
PTHREAD$RTL THD_INIT pthread_main 243137 00000000000006C0 FFFFFFFF844F86C0
0 FFFFFFFF80B65120 FFFFFFFF80B65120
DCL 0 000000000006BA90 000000007AE0BA90
%TRACE-I-LINENUMBER, Leading '#' specifies a source file record number.
%TRACE-I-END, end of TRACE stack dump
Any hints from someone where I should start looking for reason for below access violation?
It is a new program. Does it require some more quota or. What is most common reason for "access violation"?
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0000000000110000, PC=FF
FFFFFF84260D11, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBOTS 0 0000000000012D11 FFFFFFFF84260D11
libclntsh ttcx2y ttcc2u 427560 0000000000002110 000000000135D230
libclntsh ttcx2y ttcs2c 429560 000000000000ED20 0000000001369E40
libclntsh ttcacs ttcacr 415042 0000000000005DD0 00000000013587F0
libclntsh ttcdrv ttcdrv 1433700 0000000000002BC0 000000000139B080
libclntsh nioqwa nioqwa 162140 00000000000000C0 0000000000A62420
libclntsh upiprv upirtrc 418061 0000000000002300 000000000069C200
libclntsh kpurc kpurcsc 396905 00000000000001B0 00000000005A84F0
libclntsh kpuex kpuexecv8 1056507 0000000000009030 00000000004F9920
libclntsh kpuex kpuexec 1057935 000000000000FD50 0000000000500640
libclntsh oci8 OCIStmtExecute #1182 00000000000020F0 0000000000238A50
FBFSSND 0 000000000008FC70 000000000008FC70
FBFSSND 0 0000000000071D80 0000000000071D80
FBFSSND 0 00000000000507F0 00000000000507F0
FBFSSND 0 0000000000051AB0 0000000000051AB0
FBFSSND 0 0000000000052A30 0000000000052A30
FBFSSND 0 0000000000053E20 0000000000053E20
FBFSSND 0 0000000000053F50 0000000000053F50
FBFSSND 0 00000000000BDD00 00000000000BDD00
FBFSSND 0 00000000000CA3B0 00000000000CA3B0
PTHREAD$RTL THD_THREAD thdBase 243309 0000000000005BF0 FFFFFFFF84541440
PTHREAD$RTL THD_INIT pthread_main 243137 00000000000006C0 FFFFFFFF844F86C0
0 FFFFFFFF80B65120 FFFFFFFF80B65120
DCL 0 000000000006BA90 000000007AE0BA90
%TRACE-I-LINENUMBER, Leading '#' specifies a source file record number.
%TRACE-I-END, end of TRACE stack dump
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2008 03:12 AM
тАО12-17-2008 03:12 AM
Solution
An access violation is the memory management system stopping you doing something.
reason mask=04 : attempt to write readonly memory.
PC=FFFFFFFF84260D11 : you were in a system library at the time.
virtual address=0000000000110000, somewhere in your program. A suspiciously round number, suggesting you might have wandered across a page boundary.
So, fire up a debugger, or put debug prints in your code. Work from the top of the call stack, and double check what parameters you are passing to the system library.
reason mask=04 : attempt to write readonly memory.
PC=FFFFFFFF84260D11 : you were in a system library at the time.
virtual address=0000000000110000, somewhere in your program. A suspiciously round number, suggesting you might have wandered across a page boundary.
So, fire up a debugger, or put debug prints in your code. Work from the top of the call stack, and double check what parameters you are passing to the system library.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2008 03:29 AM
тАО12-17-2008 03:29 AM
Re: access violation
Klaes-G├Г┬╢ran,
the ACCVIO itself happens in LIBOTS, a system library, after being called from a routine in an ORACLE library (libclntsh). If your code is in image FBFSSND, use a linker map and the source and machine-code listings to find out about the call with return address 8FC70.
You can also use $ SET PROC/DUMP before running this image to obtain a process dump in case of an improperly handled condition. You can then analyze the process dump with $ ANAL/PROC.
Volker.
the ACCVIO itself happens in LIBOTS, a system library, after being called from a routine in an ORACLE library (libclntsh). If your code is in image FBFSSND, use a linker map and the source and machine-code listings to find out about the call with return address 8FC70.
You can also use $ SET PROC/DUMP before running this image to obtain a process dump in case of an improperly handled condition. You can then analyze the process dump with $ ANAL/PROC.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2008 03:55 AM
тАО12-17-2008 03:55 AM
Re: access violation
Thanks for your answers! Problem caused by c-program and pointer to pointers pointing on ... god nows what...
MERRY CHRISTMAS
Klaes-G├╢ran
MERRY CHRISTMAS
Klaes-G├╢ran
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP