Closed Bug 37035 Opened 25 years ago Closed 25 years ago

[PP] assertion nsDateTimeFormatUnix not thread-safe

Categories

(Core :: Internationalization, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: nhottanscp)

Details

###!!! ASSERTION: nsDateTimeFormatUnix not thread-safe: 'owningThread == 
NS_CurrentThread()', file nsDebug.cpp, line 374
  ###!!! Break: at file nsDebug.cpp, line 374
  ###!!! ASSERTION: nsDateTimeFormatUnix not thread-safe: 'owningThread == 
NS_CurrentThread()', file nsDebug.cpp, line 374
  ###!!! Break: at file nsDebug.cpp, line 374

this should fix it:

Index: nsDateTimeFormatUnix.cpp
===================================================================
RCS file: /cvsroot/mozilla/intl/locale/src/unix/nsDateTimeFormatUnix.cpp,v
retrieving revision 1.26
diff -p -r1.26 nsDateTimeFormatUnix.cpp
*** nsDateTimeFormatUnix.cpp    2000/04/13 20:08:57     1.26
--- nsDateTimeFormatUnix.cpp    2000/04/25 00:59:39
*************** static NS_DEFINE_IID(kICharsetConverterM
*** 41,47 ****
  static NS_DEFINE_CID(kLocaleServiceCID, NS_LOCALESERVICE_CID);
  static NS_DEFINE_CID(kPlatformCharsetCID, NS_PLATFORMCHARSET_CID);

! NS_IMPL_ISUPPORTS(nsDateTimeFormatUnix, kIDateTimeFormatIID);

  // init this interface to a specified locale
  nsresult nsDateTimeFormatUnix::Initialize(nsILocale* locale)
--- 41,47 ----
  static NS_DEFINE_CID(kLocaleServiceCID, NS_LOCALESERVICE_CID);
  static NS_DEFINE_CID(kPlatformCharsetCID, NS_PLATFORMCHARSET_CID);

! NS_IMPL_THREADSAFE_ISUPPORTS(nsDateTimeFormatUnix, kIDateTimeFormatIID);

  // init this interface to a specified locale
  nsresult nsDateTimeFormatUnix::Initialize(nsILocale* locale)
this is a linux only bug.
OS: Windows NT → Linux
Summary: assertion nsDateTimeFormatUnix not thread-safe → [PP] assertion nsDateTimeFormatUnix not thread-safe
nhotta, please take care this .Thanks.
Assignee: ftang → nhotta
Status: NEW → ASSIGNED
Checked in, the assertion is gone, thanks for the patch.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
QA Contact: teruko → nhotta
verified, the assertion is gone.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.