Bugs item #1571541, was opened at 2006-10-05 16:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1571541&group_id=7586 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: threads Group: None Status: Open Resolution: None Priority: 5 Submitted By: Glen Summers (glensummers) Assigned to: Mike Glassford (glassfordm) Summary: thread_resource_error exceptions do not store os errorcodes Initial Comment: one example would be in the thread constructor: In a BOOST_HAS_WINTHREADS build The OS level error code from _beginthreadex is available via a call to the crt's __doserrno() ideally this would be passed to the thread_resource_error's constructor that takes an os error code, namely: thread_resource_error::thread_resource_error(int sys_err_code); then thread_exception::message (if it didnt also have a bug) could be used to get a meaningful error message ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1571541&group_id=7586 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs