• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
thread safety of C++ standard library
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

thread safety of C++ standard library


  • Subject: thread safety of C++ standard library
  • From: John Weeks <email@hidden>
  • Date: Tue, 1 Dec 2009 13:36:19 -0800

In particular, is std::sort thread-safe when working with distinct
containers? That is, std::sort(iterator, iterator, predicate) where the
iterators point to different containers.

Xcode 3.12, 10.4 SDK, gcc 4.0

std::sort needs write access to the containers, but they are different
containers.

I seem to be getting a deadlock in the iterator allocators. The problem is
much more likely in a debug build. I see in the iterator class something
that looks like a linked list of iterators. Is that my problem?

And where would I find this information myself?

Thank you!

Regards,
John Weeks

WaveMetrics, Inc.
Phone (503) 620-3001
Fax   (503) 620-6754
email   email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: thread safety of C++ standard library
      • From: Rush Manbert <email@hidden>
    • Re: thread safety of C++ standard library
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Re: Converting Xcode paths to usable paths
  • Next by Date: agvtool auto generated version source file - where art thou ?
  • Previous by thread: Re: How to deal with missing function on Leopard
  • Next by thread: Re: thread safety of C++ standard library
  • Index(es):
    • Date
    • Thread