Conference turris::decc

2087.0. "ACCVIO on warning statement." by CSC32::EHA (Flip) Fri Feb 07 1997 17:11

    Hello,
    
    I have a customer that is compiling with the DEC C compiler, V5.5-002,
    on an Alpha VMS 6.2 machine.  The code is not good and has an odvious
    error in it, but is should not cause an accvio when compiling. 
    
    The following is the log file of the compile I did on our test systems: 
    
$ on warning then goto clean_up
$ create bprintf.c
int bprintf(
	char *bufp,
	int len,
	char *fmt,
	...
);

int
bprintf(bufp, len, fmt, va_alist)
char *bufp;
int len;
char *fmt;
{
}
$ cc bprintf

bprintf(bufp, len, fmt, va_alist)
^
%CC-W-FUNCREDECL, In this declaration, function types differ because one has no argument information and the other has ellipsis.
at line number 9 in file XWINGS$DKA100:[EHA.WORK]BPRINTF.C;4
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=0019AE54, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC           abs PC      
 DECC$COMPILER                              0 000000000018AE54 000000000019AE54
 DECC$COMPILER                              0 0000000000163EA4 0000000000173EA4
 DECC$COMPILER                              0 00000000001407DC 00000000001507DC
 DECC$COMPILER  GEM_CP_VMS  GEM_CP_MAIN
                                         2509 00000000000015C4 0000000000235B14
                                            0 FFFFFFFF833C2170 FFFFFFFF833C2170
$clean_up:
$ ver = f$verify(ver)
    
    Is this a valid feature?
    
    Thank you!
    Al Eha

This is still a problem in the mainline development compiler. I was able to
reproduce it on UNIX, as well. I will report this in the internal bugtracking
system as cxxc_bugs 4124.

The compiler should never crash, even when dealing with broken code.
Thanks for reporting the problem

-Jeff

    
    This problem has been corrected in our internal compiler sources.
    
    This fix should be included in the SSB version of DEC C V5.6.
    
    Thank you for finding this problem,  we regret any difficulty it
    caused you and/or your customer.
    
    						Ed