From: Carlo W. <li...@us...> - 2002-02-21 20:17:33
|
CVSROOT : /cvsroot/libcw Module : src Commit time: 2002-01-21 20:17:30 UTC Modified files: libcwd/documentation/allocated_memory_overview.dox libcwd/documentation/memory_leak_checking.dox libcwd/include/libcw/class_location.h libcwd/tests/Makefile.am Log message: Several minor fixes. ---------------------- diff included ---------------------- Index: src/libcwd/documentation/allocated_memory_overview.dox diff -u src/libcwd/documentation/allocated_memory_overview.dox:1.3 src/libcwd/documentation/allocated_memory_overview.dox:1.4 --- src/libcwd/documentation/allocated_memory_overview.dox:1.3 Wed Feb 20 18:05:31 2002 +++ src/libcwd/documentation/allocated_memory_overview.dox Thu Feb 21 12:17:20 2002 @@ -100,7 +100,7 @@ This is the value returned by the allocator (<CODE>malloc</CODE>, <CODE>new</CODE> etc). Note that, when \ref enable_libcwd_magic "CWDEBUG_MAGIC" is set, a magic number is put <I>in front of</I> this hexadecimal start address. -The result is that you can ignore completely whether or not CWDEBUG_MAGIC is 1, in your own program. +The result is that you can ignore completely whether CWDEBUG_MAGIC is 0 or 1, in your own program. \subsection AMO_location source file location Index: src/libcwd/documentation/memory_leak_checking.dox diff -u src/libcwd/documentation/memory_leak_checking.dox:1.3 src/libcwd/documentation/memory_leak_checking.dox:1.4 --- src/libcwd/documentation/memory_leak_checking.dox:1.3 Wed Feb 20 18:05:31 2002 +++ src/libcwd/documentation/memory_leak_checking.dox Thu Feb 21 12:17:20 2002 @@ -28,7 +28,7 @@ Any allocation done \em after the creation of this marker will be reported as a <B>leak</B> at the moment the \em marker is deleted. Markers are clearly visibly in the Allocated memory Overview. -They are labeled MARKER (see also table FIXME). +They are labeled MARKER (see also the <A HREF="group__group__overview.html#AMO_allocator">allocator type</A> table). All memory that is allocated after a \em marker, is displayed indented and below that marker in the Allocated memory Overview. Finally, it is possible to move specific memory blocks outside markers, so they will not cause a memory leak detection. Index: src/libcwd/include/libcw/class_location.h diff -u src/libcwd/include/libcw/class_location.h:1.5 src/libcwd/include/libcw/class_location.h:1.6 --- src/libcwd/include/libcw/class_location.h:1.5 Sun Feb 17 17:24:47 2002 +++ src/libcwd/include/libcw/class_location.h Thu Feb 21 12:17:20 2002 @@ -1,4 +1,4 @@ -// $Header: /cvsroot/l/li/libcw/src/libcwd/include/libcw/class_location.h,v 1.5 2002/02/18 01:24:47 libcw Exp $ +// $Header: /cvsroot/l/li/libcw/src/libcwd/include/libcw/class_location.h,v 1.6 2002/02/21 20:17:20 libcw Exp $ // // Copyright (C) 2000 - 2002, by // @@ -49,7 +49,7 @@ * The normal usage of this class is to print file-name:line-number information as follows: * \code * Dout(dc::notice, "Called from " << - * location_ct((char*)__builtin_return_address(0) + libcw::builtin_return_address_offset) ); + * location_ct((char*)__builtin_return_address(0) + libcw::debug::builtin_return_address_offset) ); * \endcode */ class location_ct { Index: src/libcwd/tests/Makefile.am diff -u src/libcwd/tests/Makefile.am:1.21 src/libcwd/tests/Makefile.am:1.22 --- src/libcwd/tests/Makefile.am:1.21 Sun Feb 17 21:07:22 2002 +++ src/libcwd/tests/Makefile.am Thu Feb 21 12:17:20 2002 @@ -8,6 +8,7 @@ threads3 \ threads4 \ hello_world \ +location \ syslog \ initbug \ dout_alloc \ @@ -19,6 +20,7 @@ CLEANFILES=$(EXTRA_PROGRAMS) hello_world_SOURCES = hello_world.cc +location_SOURCES = location.cc syslog_SOURCES = syslog.cc initbug_SOURCES = initbug.cc initbug_GlobalObject.cc dout_alloc_SOURCES = dout_alloc.cc ----------------------- End of diff ----------------------- |