josh/TCPlayerbotCore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Dep/ACE: Upgrade ACE -library to 5.8.3

Browse Source 
--HG--
branch : trunk
This commit is contained in:
click
2010-11-04 05:30:29 +01:00
parent 2604250c3c
commit 9b16ee203f
581 changed files with 10265 additions and 14303 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dep/acelite/ace/Stack_Trace.h
+12 -12
View File
@@ -3,7 +3,7 @@
/**
* @file Stack_Trace.h
*
* $Id: Stack_Trace.h 81926 2008-06-12 14:43:09Z mitza $
* $Id: Stack_Trace.h 91743 2010-09-13 18:24:51Z johnnyw $
*
* @author Chris Cleeland (cleeland.ociweb.com)
*/
@@ -37,31 +37,31 @@
* A new conversion character, the question mark, was added to ACE_Log_Msg for stack
* trace logging. The %? conversion character was added as a convenience so that users
* need not instantiate an ACE_Stack_Trace instance solely for the purpose of printing
* it in an ACE logging message. The following are functionally equivalent:
* it in an ACE logging message. The following are functionally equivalent:
*
* \code
* ACE_DEBUG((LM_DEBUG, "%?"));
* ACE_DEBUG((LM_DEBUG, "%?"));
*
* ACE_Stack_Trace st;
* ACE_DEBUG ((LM_DEBUG, "%s", st.c_str() ));
* ACE_DEBUG ((LM_DEBUG, "%s", st.c_str() ));
* \endcode
*
* These usage examples were shown in $ACE_ROOT/tests/Stack_Trace_Test.cpp.
*
* @note The stack trace functionality was currently supported on platforms:
* - Any platform using glibc as its runtime library, or where ACE_HAS_EXECINFO_H is defined
* - Any platform using glibc as its runtime library, or where ACE_HAS_EXECINFO_H is defined
* (this covers Linux and Mac) and gcc version >= 3.3.
* - VxWorks, both kernel and RTP
* - Solaris
* - Windows 32 and 64 bit (Visual C++, excluding WinCE/mobile)
*
* @note Since stack trace buffer size has limitation(@c ACE_STACK_TRACE_SYMBUFSIZ), you will not
* get a complete stack trace if @c ACE_STACK_TRACE_SYMBUFSIZ value is less than actual stack
* trace data length. To get a complete stack trace, you need set @c ACE_STACK_TRACE_SYMBUFSIZ
* with a larger value that is enough for the stack trace data in your @c config.h file
* @note Since stack trace buffer size has limitation(@c ACE_STACK_TRACE_SYMBUFSIZ), you will not
* get a complete stack trace if @c ACE_STACK_TRACE_SYMBUFSIZ value is less than actual stack
* trace data length. To get a complete stack trace, you need set @c ACE_STACK_TRACE_SYMBUFSIZ
* with a larger value that is enough for the stack trace data in your @c config.h file
* and rebuild ACE.
*
* @note Using ACE logging mechanism (%?) to log the stack trace also has ACE_MAXLOGMSGLEN size limitation.
* @note Using ACE logging mechanism (%?) to log the stack trace also has ACE_MAXLOGMSGLEN size limitation.
* To get a complete stack trace, you could use different output method. Following is an example.
*
* \code
@@ -75,8 +75,8 @@ public:
/**
* @brief Grab a snapshot of the current stack trace and hold it for later use.
*
* @param starting_frame_offset offset into the array of frames to start printing; 0 is the
* platform-specific offset for the first frame, positive numbers give less frames, negative give
* @param starting_frame_offset offset into the array of frames to start printing; 0 is the
* platform-specific offset for the first frame, positive numbers give less frames, negative give
* more frames
* @param num_frames the number of stack frames to include (0 indicates platform-specific maximum)
*