The cvar2 test calls PR_WaitCondVar in if statements

REOPENED
Assigned to

Status

defect
P1
normal
REOPENED
16 years ago
13 years ago

People

(Reporter: wtc, Assigned: wtc)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Assignee

Description

16 years ago
PR_WaitCondVar must always be called in a while loop.

I am surprised to find out that the cvar2 test calls
PR_WaitCondVar in if statements in two places.  Sigh.
Assignee

Comment 1

16 years ago
Assignee

Comment 2

16 years ago
Fix checked into the tip of NSPR.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [4.3.1]
Target Milestone: --- → 4.3
Assignee

Comment 3

16 years ago
Reopened the bug.  The patch caused the cvar2.c test
to hang in the timeout test, which expects the
PR_WaitCondVar call to be called only once.
Status: RESOLVED → REOPENED
Priority: -- → P1
Resolution: FIXED → ---
Target Milestone: 4.3 → 4.4
Assignee

Updated

16 years ago
Whiteboard: [4.3.1]
Target Milestone: 4.4 → ---
QA Contact: wtchang → nspr
You need to log in before you can comment on or make changes to this bug.