Closed Bug 559535 Opened 15 years ago Closed 15 years ago

e10s: valgrind reports uninitialized value in NSS code

Categories

(Core :: Security: PSM, defect)

Product:
Core
Component:
Security: PSM
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 538531

People

(Reporter: jdm, Assigned: KaiE)

Details

==16008== Thread 9: ==16008== Conditional jump or move depends on uninitialised value(s) ==16008== at 0x6890D69: sec_asn1e_write_contents (secasn1e.c:1108) ==16008== by 0x68910E6: SEC_ASN1EncoderUpdate_Util (secasn1e.c:1279) ==16008== by 0x689149F: SEC_ASN1Encode_Util (secasn1e.c:1467) ==16008== by 0x68916FB: SEC_ASN1EncodeItem_Util (secasn1e.c:1566) ==16008== by 0x675E5CA: PK11_FindCertByIssuerAndSN (pk11cert.c:1579) ==16008== by 0x6798E93: CERT_FindCertByIssuerAndSN (stanpcertdb.c:497) ==16008== by 0x53B7423: nsNSSComponent::IdentityInfoInit() (nsIdentityChecking.cpp:834) ==16008== by 0x605226C: PR_CallOnce (prinit.c:807) ==16008== by 0x53B810C: nsNSSComponent::EnsureIdentityInfoLoaded() (nsIdentityChecking.cpp:1162) ==16008== by 0x53B7AB5: nsNSSCertificate::hasValidEVOidTag(SECOidTag&, int&) (nsIdentityChecking.cpp:986) ==16008== by 0x53B7EC6: nsNSSCertificate::getValidEVOidTag(SECOidTag&, int&) (nsIdentityChecking.cpp:1102) ==16008== by 0x53B7FDD: nsNSSCertificate::GetIsExtendedValidation(int*) (nsIdentityChecking.cpp:1128) ==16008== ==16008== Conditional jump or move depends on uninitialised value(s) ==16008== at 0x6890D69: sec_asn1e_write_contents (secasn1e.c:1108) ==16008== by 0x68910E6: SEC_ASN1EncoderUpdate_Util (secasn1e.c:1279) ==16008== by 0x689149F: SEC_ASN1Encode_Util (secasn1e.c:1467) ==16008== by 0x68917A2: SEC_ASN1EncodeItem_Util (secasn1e.c:1581) ==16008== by 0x675E5CA: PK11_FindCertByIssuerAndSN (pk11cert.c:1579) ==16008== by 0x6798E93: CERT_FindCertByIssuerAndSN (stanpcertdb.c:497) ==16008== by 0x53B7423: nsNSSComponent::IdentityInfoInit() (nsIdentityChecking.cpp:834) ==16008== by 0x605226C: PR_CallOnce (prinit.c:807) ==16008== by 0x53B810C: nsNSSComponent::EnsureIdentityInfoLoaded() (nsIdentityChecking.cpp:1162) ==16008== by 0x53B7AB5: nsNSSCertificate::hasValidEVOidTag(SECOidTag&, int&) (nsIdentityChecking.cpp:986) ==16008== by 0x53B7EC6: nsNSSCertificate::getValidEVOidTag(SECOidTag&, int&) (nsIdentityChecking.cpp:1102) ==16008== by 0x53B7FDD: nsNSSCertificate::GetIsExtendedValidation(int*) (nsIdentityChecking.cpp:1128) ==16008== Running with valgrind --trace-children=yes and NECKO_E10S_HTTP=1. I don't remember seeing this before some of the recent changes to make the test shell work, so I'm assuming it's caused by something necko's doing.
The data that ends up in sec_asn1e_write_contents doesn't obviously come from necko.....
Assignee: nobody → nobody
Component: Networking → Libraries
Product: Core → NSS
QA Contact: networking → libraries
Yes, it does.
Assignee: nobody → kaie
Status: NEW → RESOLVED
Closed: 15 years ago
Component: Libraries → Security: PSM
Product: NSS → Core
QA Contact: libraries → psm
Resolution: --- → DUPLICATE
Actually, no. It doesn't. It comes from PSM, per bug 538531. That's not the same thing as necko, by a long shot.
You need to log in before you can comment on or make changes to this bug.