(9917) Resolving Memory Management Violations? (ACCVIO)

Archive of the OpenVMS Ask the Wizard (ATW) questions and answers database.
Locked

Topic author
User
Visitor
Posts: 0
Joined: Mon Jan 10, 2022 8:16 am
Reputation: 0
Status: Offline

(9917) Resolving Memory Management Violations? (ACCVIO)

Post by User » Sun Nov 28, 2004 8:26 am

Why is this error comming up and how to resolve this?
Erro Message :

Code: Select all

%BAS-F-MEMMANVIO, Memory management violation
-BAS-I-USEPC_PSL, at user PC=00016121, PSL=03C000A0
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=00016121, PSL=03C000A0
-BAS-I-FROLINGSB, from line 2200 in GOSUB 2200 in module PIE
-BAS-I-FROLINMOD, from line 1005 in module PIE
%TRACE-F-TRACEBACK, symbolic stack dump follows
image    module    routine   line      rel PC           abs PC
                                                          00078F0F    00078F0F 
 ----- above condition handler called with exception 001A811C:
 %BAS-F-MEMMANVIO, Memory management violation
-BAS-I-USEPC_PSL, at user PC=00016121, PSL=03C000A0
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=00016121, PSL=03C000A0
-BAS-I-FROLINGSB, from line 2200 in GOSUB 2200 in module PIE
----- end of exception message 
                                                          00078F0F    00078F0F
----- above condition handler called with exception 0000000C:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=00016121, PSL=03C000A0
 ----- end of exception message
            PIE$MAIN        PIE$MAIN
            3910      00001721   00016121
            PIE$MAIN        PIE$MAIN
            3652     00000971  000
            15371
Last edited by marty.stu on Wed Jan 12, 2022 4:17 am, edited 2 times in total.


Wizard
Visitor
Posts: 0
Joined: Mon Jan 10, 2022 8:17 am
Reputation: 0
Status: Offline

Re: (9917) Resolving Memory Management Violations? (ACCVIO)

Post by Wizard » Mon Nov 29, 2004 8:26 am

The specified code appears to contain one or more bugs, and particularly appears to contain a run-time stack corruption or other similar error. For other discussions of related programming problems -- for some of the various coding errors that are possible -- please see topics including (9450) and (1661).

If you are not directly maintaining the source code involved here, please contact the organization that is supporting the application. The general resolution of errors such as this one almost invariably involve at least some degree of access to the source code involved, of course, and can require rebuilding the application source code after coding a fix.
Last edited by marty.stu on Wed Jan 12, 2022 4:19 am, edited 1 time in total.

Locked