You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.



NSPR 4.1.1 Release

18-May-2001


Table of Contents

  1. Introduction
  2. Changes in this release
  3. Reporting bugs
  4. Building from source
  5. Contact Info

1. Introduction

The NSPR 4.1.1 release is now available at /share/builds/components/nspr20/v4.1.1. This release is a patch release for the NSPR 4.1 release.

2. Changes in this release

2.1 Bug fixes

The following bugs are fixed in this release.

BugZilla #51406. Backward compatibility, PR_GetConnectStatus with NSPR 4.0
BugZilla #51743. PR_EnterMonitor() makes an unnecessary pthread_mutex_trylock
BugZilla #54796. PR_InitializeNetAddr() does not clear trailing garbage
Bugzilla #62457. fcntl file locking needs to set other fields in struct flock
Bugzilla #63273. PR_Assert() should be defined in optimized builds.
Bugzilla #64278. ptthread.c assertion failure on startup
Bugzilla #64471. PR_Sendfile() should use sendfilev() on Solaris
Bugzilla #66325. PR_LoadLibrary() picks up same named file
Bugzilla #70295. PR_LockFile()/PR_UnlockFile() deadlock.
Bugzilla #70381. PR_StringToNetAddr and PR_Bind on OSF/1
Bugzilla #45343. PLArena problems. [Note: the bugzilla describes several problems with PLArena. Some were fixed and included in 4.1.1, some were not. See the report for the particulars. 27-Jun-2001, larryh]
Bugzilla #70765. PR_Writes misbehaves when writing to Network drives from NT

 3. Reporting bugs

Bugs discovered should be reported by filing bug reports.  If you can describe a bug without giving any proprietary information, you should file the bug report in mozilla.org's bug database Bugzilla.  You will need a Bugzilla account, which can be obtained easily from the Bugzilla main page.  If proprietary information cannot be avoided in a bug description, you can file the bug report in Bugsplat.

The following information is required in a bug report

  • platform (Solaris 2.6, HP-UX 11.0, etc.)
  • number of cpus in the system
  • a stack trace, in the event of a crash
  • reproducibility of the problem
  • location of core dump, if available, along with those for the libraries and executables

 4. Building from source

This release is built from the source at the CVS repository cvs.mozilla.org:/cvsroot with the CVS tag NSPRPUB_RELEASE_4_1_1. Check out the source from CVS by

    cvs co -r NSPRPUB_RELEASE_4_1_1 mozilla/nsprpub

To build, do
    cd mozilla/nsprpub
    gmake export

5. Contact Info

See NSPR Project Contacts