Access Violation in QUICK screens

[Hamilton, Allison]

I think it's important to note here that ACCVIO is a VERY generic error on
VMS and can be caused by any number of things going wrong. All ACCVIO's are
definitely not the same, and the specifics must be compared to see if one
fix is likely to affect a problem anyone else is having.  I know that we've
discovered a number of problems caused by some incorrect handling of
variable length records over the last year.  All of which cause, usually
unreproducable, ACCVIO's.  We were only able to find the cause with some
extremely patient and cooperative assistance from a couple of customers.
Finding the cause(s) took some pretty extreme debugging methods.  These
problems are relatively easy to debug if we have a reproducable scenario,
and like looking for a needle in a haystack when we don't.

I personnally want to thank all of you who take the time to give us a test
case.  I've been out there and I know how much of a pain it can be.  But,
from the viewpoint of someone who gets to find these wonderful little
oddities, it sure makes it easier (and in some cases the only possible way)
to fix the problem and get on to the next one when I can see the cause.  
Allison Hamilton
My opinions my own - I won't let anyone else lay claim to it - but then why
would they want to?
> ----------
> From: 	Hamilton, Allison[SMTP:Allison.Hamilton@Cognos.COM]
> Sent: 	Tuesday, September 21, 1999 3:38 PM
> To: 	'powerh-l@lists.swau.edu'; 'Karl Hoppe'
> Subject: 	RE: Access Violation in QUICK screens
> 
> Let me clarify that by programming error - I meant that it is an internal
> PowerHouse coding error - in C, not an external PowerHouse user
> programming
> error.
> Allison Hamilton
> 
> > ----------
> > From: 	Hamilton, Allison[SMTP:Allison.Hamilton@Cognos.COM]
> > Sent: 	Tuesday, September 21, 1999 2:49 PM
> > To: 	'powerh-l@lists.swau.edu'; 'Karl Hoppe'
> > Subject: 	RE: Access Violation in QUICK screens
> > 
> > Karl, This is an access violation in VMS, which means that the product
> > accessed some place in memory when it shouldn't have.  This is usually a
> > programming error.  If you have a reproducable test case, please log it.
> > These are very hard to find without a test case.  Unless we can identify
> > the
> > specific cause of the fault, there is usually no user action that can
> > avoid
> > this problem.
> > 
> > Allison Hamilton
> > 
> > > ----------
> > > From: 	Karl Hoppe[SMTP:KHoppe@resourcephoenix.com]
> > > Sent: 	Tuesday, September 21, 1999 2:32 PM
> > > To: 	'powerh-l@lists.swau.edu'
> > > Subject: 	Access Violation in QUICK screens
> > > 
> > > can anyone help me understand the nature of this error message and how
> > to
> > > correct the fault?
> > > 
> > > %SYSTEM--E--ACCVIO, access violation, reason mask=!XB, virtual
> > > address=!XH,
> > > PC=!XL
> > > %NONAME-W-NOMSG, Message number 00000000
> > > %SYSTEM-F-ABORT, about
> > > 
> > > 
> > > This seems to be related to release 7.10.G2 on the DEC Alpha platform.
> > We
> > > got it more frequently with G1 and the upgrade to G2 helped some, not
> > > completely.
> > > 
> > > Thanks,
> > > 
> > > Karl Hoppe
> > > STHR Team
> > > ReSourcePhoenix.com
> > > (415) 485-4662
> > > KHOPPE@RESOURCEPHOENIX.COM
> > > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > =
> > > =
> > > Subscribe: "subscribe powerh-l" in message body to
> > > majordomo@lists.swau.edu
> > > Unsubscribe: "unsubscribe powerh-l" in message to
> > majordomo@lists.swau.edu
> > > This list is closed, thus to post to the list, you must be a
> subscriber.
> > > 
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> > =
> > Subscribe: "subscribe powerh-l" in message body to
> > majordomo@lists.swau.edu
> > Unsubscribe: "unsubscribe powerh-l" in message to
> majordomo@lists.swau.edu
> > This list is closed, thus to post to the list, you must be a subscriber.
> > 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> This list is closed, thus to post to the list, you must be a subscriber.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.