------- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-16
19:47 -------
With -fmudflap, I get errors (many of them but this is with i686-pc-linux):
*******
mudflap violation 1 (check/write): time=1121543018.141782 ptr=0xbfe049c0 size=4
pc=0xed9eb8
location=`/home/data/redi/gcc/bin/4.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/
4.0.2/../../../../include/c++/4.0.2/bits/stl_list.h:203
(std::_List_const_iterator<void*>::
_List_const_iterator)'
/home/peshtigo/pinskia/linux/lib/libmudflap.so.0(__mf_check+0x48)
[0xed9eb8]
./a.out(_ZNSt20_List_const_iteratorIPvEC1EPKSt15_List_node_base+0x6f)
[0x804f339]
./a.out(_ZNKSt4listIPvSaIS0_EE3endEv+0x19) [0x804f35d]
Nearby object 1: checked region begins 12B before and ends 9B before
mudflap object 0x8aa3a10:
name=`/home/data/redi/gcc/bin/4.0/bin/../lib/gcc/x86_64-unknown-
linux-gnu/4.0.2/../../../../include/c++/4.0.2/bits/stl_list.h:656
(std::list<void*, std::allocator<void*>
>::size) <unnamed variable>'
bounds=[0xbfe049cc,0xbfe049cf] size=4 area=stack check=0r/0w liveness=0
alloc time=1121543018.141767 pc=0xed9128
Nearby object 2: checked region begins 16B before and ends 13B before
mudflap object 0x8aa3a60:
name=`/home/data/redi/gcc/bin/4.0/bin/../lib/gcc/x86_64-unknown-
linux-gnu/4.0.2/../../../../include/c++/4.0.2/bits/stl_list.h:656
(std::list<void*, std::allocator<void*>
>::size) <unnamed variable>'
bounds=[0xbfe049d0,0xbfe049d3] size=4 area=stack check=0r/0w liveness=0
alloc time=1121543018.141772 pc=0xed9128
Nearby object 3: checked region begins 29B after and ends 32B after
mudflap dead object 0x8aa3948:
name=`/home/data/redi/gcc/bin/4.0/bin/../lib/gcc/x86_64-
unknown-linux-gnu/4.0.2/../../../../include/c++/4.0.2/bits/stl_list.h:327
(std::_List_base<void*, std::
allocator<void*> >::_List_base) <unnamed variable>'
bounds=[0xbfe049a3,0xbfe049a3] size=1 area=stack check=0r/0w liveness=0
alloc time=1121543018.141709 pc=0xed9128
dealloc time=1121543018.141732 pc=0xed8c11
number of nearby objects: 3
Please try with -fmudflap -lmudflap and if you don't get an error then maybe
this is a GCC bug but if
you do get an error then this looks like a boost bug.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
GCC target triplet| |x86_64-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22513
