Re: [Boost-bugs] [Boost C++ Libraries] #9285: CreateMutex return NULL if failed

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9285: CreateMutex return NULL if failed
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-10-28 02:51:06

#9285: CreateMutex return NULL if failed
-------------------------------+--------------------------
  Reporter:  huyuguang@…       |      Owner:  igaztanaga
      Type:  Bugs              |     Status:  closed
 Milestone:  To Be Determined  |  Component:  interprocess
   Version:  Boost 1.54.0      |   Severity:  Problem
Resolution:  fixed             |   Keywords:
-------------------------------+--------------------------

Comment (by huyuguang@…):

 Replying to [comment:1 igaztanaga]:
 > Thanks for the report. It will changed to handle a nullptr.
 winapi_mutex_wrapper also shares the same bug described in your #9288
 ("timed_wait does not check if has expired") ticket.

 I suggest you remove the #define
 BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION in workaround.hpp
 #if defined(_WIN32) || defined(__WIN32__) || defined(WIN32)
    #define BOOST_INTERPROCESS_WINDOWS
    #define BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION
    #define BOOST_INTERPROCESS_HAS_KERNEL_BOOTTIME

 If a server need to handle multiple message queue, for example, 64 queues,
 the spinlock would kill too much cpu.
 Also, if possible, I hope you can implement two more function which are
 multi_timed_recv and multi_timed_send, so that I can wait multiple queue
 and do not need to lanuch many threads for every queues.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/9285#comment:3>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.