Closed
Bug 129594
Opened 23 years ago
Closed 23 years ago
tstclnt coredump after checkins in pki
Categories
(NSS :: Tools, defect, P1)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 129298
3.4
People
(Reporter: sonja.mirtitsch, Assigned: wtc)
Details
Attachments
(1 file)
2.69 KB,
text/plain
|
Details |
all ssl3 and tls causes immediate coredump.
will attach output log and stacktrace
tstclnt -p 8444 -h starend -c F -T \
-f -d . <
/usr11/nss_tbx_OSF1-5.0/builds/tinderbox/OSF1-5.0/mozilla/security/nss/tests/ssl/sslreq.txt
subject DN: CN=starend.red.iplanet.com, O=BOGUS Netscape, L=Mountain View,
ST=California, C=US
issuer DN: CN=NSS Test CA, O=BOGUS NSS, L=Mountain View, ST=California, C=US
0 cache hits; 0 cache misses, 0 cache not reusable
HTTP/1.0 200 OK
Server: Generic Web Server
Date: Tue, 26 Aug 1997 22:10:05 GMT
Content-type: text/plain
Discarded 1 characters.
GET / HTTP/1.0
EOF
ssl.sh: running SSL3 RSA WITH RC4 128 MD5 ----------------------------
tstclnt -p 8444 -h starend -c c -T \
-f -d . <
/usr11/nss_tbx_OSF1-5.0/builds/tinderbox/OSF1-5.0/mozilla/security/nss/tests/ssl/sslreq.txt
/usr11/nss_tbx_OSF1-5.0/builds/tinderbox/OSF1-5.0/mozilla/security/nss/tests/all.sh:
515011 Memory fault - core dumped
Reporter | ||
Updated•23 years ago
|
Severity: normal → blocker
Priority: -- → P1
Target Milestone: --- → 3.4
Reporter | ||
Comment 1•23 years ago
|
||
linux has problems in ssl2 as well
Reporter | ||
Comment 2•23 years ago
|
||
Assignee | ||
Comment 3•23 years ago
|
||
Thank you, Sonja, for the bug report.
Ian and I have looked at these test failures and have checked
in a fix. We will watch the Tinderboxes until they are all
green again.
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•23 years ago
|
||
This bug was caused by an uninitialized variable in the
first patch of bug 129298 and then by an incorrect
assertion in the subsequent checkin. Both problems
have been fixed now.
*** This bug has been marked as a duplicate of 129298 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•