[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

1856.0. "mcc_dns_opaque_fullname: suspected bug" by BYBLOS::TAMER () Mon Nov 25 1991 19:38

MCC V1.1 on VMS

mcc_dns_opaque_fullname is overwriting the character at position 
(fullname_string_len + 1) in the 'read-only' string fullname_string.

example:

fullname_string startes at memory position 1547593

fullname_string_len is 21


just before call to  mcc_dns_opaque_fullname

DBG> ex/a:1 1547614 

1547614:        'T'

and just after the call

DBG> ex/a:1 1547614 

1547614:        '.'

This results in corruption of string2 when the next string startes just
at the (string1_len + 1).

Can anyone reproduce it to make sure that it is a bug ? Or is this a known 
bug ?

Thanks,
Phil
T.RTitleUserPersonal
Name		DateLines
1856.1Yes, it was a bug.TRM::KWAKWed Nov 27 1991 14:1813
    
    RE: .0
    
    You're right. 
    In MCC V1.1, the input fullname string was forced to be null-terminated
    in mcc_dns_opaque_fullname().
    
    The correction to this problem was made a few months ago, and the
    DECmcc V1.2 will treate the input string as "read-only".
    
    Thanks.