Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

The Boost Libraries 1.37.0 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News The Boost Libraries 1.37.0 (Default branch)
# 1  
Old 12-19-2008
The Boost Libraries 1.37.0 (Default branch)
Boost was begun by members of the C++ standards committee Library Working Group to provide free peer-reviewed portable libraries to the C++ community. An additional objective is to establish "existing practice" and provide reference implementations so that the Boost libraries are suitable for eventual standardization. Indeed, the explicit intent is to propose many of these libraries for inclusion in the C++ Standard Library. The Boost Graph Library, formerly known as the Generic Graph Component Library (GGCL), is a collection of graph algorithms and data structures created in the generic programming style of the Standard Template Library (STL).License: Artistic LicenseChanges:
Many new and updated libraries.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Solaris

boost thread not accessible to boost::move error

Hi All I am working unders Sun Solaris and I am not "/opt/boost/boost/thread/detail/thread.hpp", line 344: Error: boost::thread::thread(boost::thread&) is not accessible from boost::move(boost::detail::thread_move_t<boost::thread>). Do you know if there are other solutions other than... (2 Replies)
Discussion started by: manustone
2 Replies
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

imptrace

IMPTRACE(1)						    BSD General Commands Manual 					       IMPTRACE(1)

NAME

     imptrace -- report importance donation events in real time

SYNOPSIS

     imptrace [-i [-s]] [-p pid] [-d]

DESCRIPTION

     The imptrace utility displays a trace of importance donation events. Importance donation is used by adaptive jobs on the system to manage
     their priority on the system. See xpc_transaction_begin(3) and launchd.plist(5) for more information about the mechanism and its use.

     The options are as follows:

     -i       Show internal kernel boosts

     -s       Show stacks for internal boosts.

     -p pid   Limit events to the process identified by pid.

     -d       Display raw Dtrace output; do not reformat timestamps and sort output.

     The traced events are as follows:

     BOOSTED	     The specified process has received a boost and transitioned out of the background.

     UNBOOST	     The specified process has dropped its last remaining boost and transitioned back into the background.

     Recv Boost      The specified process has received a boost and accepted ownership of that boost in userspace, usually by dequeuing the boost-
		     ing message.

     Drop Boost      The specified process has dropped a boost.

     ____ Int Boost  Internal boost events are only emitted when tracking of kernel internal boosts is activated with the -i option. Their use and
		     meaning is subject to change and dependent on the implementation details of importance donation.

EXAMPLES

     The imptrace script will output one line for each event, for example a typical boosting exchange might look as follows:

	   0000:00:00.000000000 EVENT		 PROCESS		BOOSTS NOTES
	   0023:15:13.844332886   BOOSTED	     22:configd
	   0023:15:13.844372519   Recv Boost	     22:configd 	     1 from    275:SystemUIServer
	   0023:15:13.844497860   UNBOOST	     22:configd 	       Boosted for 0 ms
	   0023:15:13.844509452   Drop Boost	     22:configd 	     0

     In this case, SystemUIServer (PID 275) has sent a message to configd (PID 22) which caused it to be boosted. configd then dropped the boost
     causing it to be become unboosted and return to background state. Boosted and unboost events may appear before the triggering recv or drop
     boost.

NOTES

     imptrace is implemented using Dtrace.  For information about the probes used, see comments in the imptrace source.  When debugging an adap-
     tive service, it may be helpful to combine these probes with other Dtrace providers; however, they should be considered unstable.

OS X
								   May 01, 2013 							      OS X