Re: [Boost-users] compatibility of boost 1.39

Subject: Re: [Boost-users] compatibility of boost 1.39
From: manish4gupta (manish_at_[hidden])
Date: 2009-10-05 02:42:01

As suggested i put bt option still ..

#0  0xa000000000010641 in __kernel_syscall_via_break ()
#1  0x20000000004ddfa0 in sched_yield () from /lib/tls/libc.so.6.1
#2  0x400000000002c3b0 in boost::interprocess::detail::thread_yield ()
    at
/usr/local/include/boost/interprocess/detail/os_thread_functions.hpp:145
#3  0x400000000002c4f0 in boost::interprocess::interprocess_mutex::lock (
    this=0x2000000000700050)
    at
/usr/local/include/boost/interprocess/sync/emulation/interprocess_mutex.hpp:39
#4  0x40000000000375b0 in
boost::interprocess::interprocess_recursive_mutex::lock
(this=0x2000000000700050)
    at
/usr/local/include/boost/interprocess/sync/emulation/interprocess_recursive_mutex.hpp:54
#5  0x40000000000376c0 in scoped_lock (this=0x60000fffffffa730, 
    m=@0x2000000000700050)
    at /usr/local/include/boost/interprocess/sync/scoped_lock.hpp:78
#6  0x400000000003b250 in boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index>::priv_generic_named_construct<char>
(this=0x2000000000700010, type=1, 
    name=0x4000000000040030 "MyMap", num=1, try2find=false, dothrow=true, 
    table=@0x60000fffffffa8c0, index=@0x2000000000700068, is_intrusive=
      {<boost::interprocess::detail::integral_constant<bool,true>> = {static
value = <optimized out>}, static value = <optimized out>})
---Type <return> to continue, or q <return> to quit---
    at /usr/local/include/boost/interprocess/segment_manager.hpp:1071
#7  0x400000000003bfb0 in boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index>::priv_generic_construct
(this=0x2000000000700010, name=0x4000000000040030 "MyMap", num=1, 
    try2find=false, dothrow=true, table=@0x60000fffffffa8c0)
    at /usr/local/include/boost/interprocess/segment_manager.hpp:743
#8  0x400000000003c0f0 in boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index>::generic_construct<boost::interprocess_container::multimap<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > >,
boost::interprocess_container::basic_string<char, std::char_traits<char>,
boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > >,
std::less<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > >,
boost::interprocess::allocator<std::pair<boost::interprocess_co---Type
<return> to continue, or q <return> to quit---
ntainer::basic_string<char, std::char_traits<char>,
boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > const,
boost::interprocess_container::basic_string<char, std::char_traits<char>,
boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > >,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > > (this=0x2000000000700010,
name=0x4000000000040030 "MyMap", num=1, 
    try2find=false, dothrow=true, table=@0x60000fffffffa8c0)
    at /usr/local/include/boost/interprocess/segment_manager.hpp:684
#9  0x400000000003c280 in
boost::interprocess::detail::named_proxy<boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index>,
boost::interprocess_container::multimap<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > >,
boost::interprocess_container::basic_string<char, std::char_traits<char>,
boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit---Type <return> to continue, or q
<return> to quit---
<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void>,
0ul>, boost::interprocess::iset_index> > >,
std::less<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > >,
boost::interprocess::allocator<std::pair<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > const,
boost::interprocess_container::basic_string<char, std::char_traits<char>,
boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > >,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > >,
false>::operator()<std::less<boost::interprocess_container::basic_string<char,
std::char_traits<char>, boost::interprocess::allocator<char,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>,
boost::interprocess::iset_index> > > >, boost::interprocess::allocator<void,
boost::interprocess::segment_manager<char,
boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family,
boost::interprocess::offset_ptr<void>, 0ul>---Type <return> to continue, or
q <return> to quit---
, boost::interprocess::iset_index> > > (this=0x60000fffffffa9b8, 
    p0=@0x60000fffffffa9a9, p1=@0x60000fffffffa9d8)
    at /usr/local/include/boost/preprocessor/iteration/detail/local.hpp:40
#10 0x4000000000002f00 in main (argc=1, argv=0x60000fffffffb8a8)
    at boostindex.cpp:24
I am getting the above on keeping bt.Please suggest what can i do. Since
this is beyond my understanding.

manish4gupta wrote:
> 
> Ok I will try but still i feel the process u are using are all x86. As far
> as doc is concerned for x86 we do have example while building like address
> model and architecture but for ia64 no such example.Any as u suggested to
> recompile with debugger using bt option, I will follow that.
> 
> Roland Bock-2 wrote:
>> 
>> manish4gupta wrote:
>>> Thanks...
>>> 
>>> May i Know do u have Ia64 machine so that i can again look it into it ..
>> 
>> Intel Xeon QuadCore, DualCore and some 64bit AMD single core machine. I 
>> doubt that the processor is to blame in your case.
>> 
>> 
>> For the debugger:
>> 
>> run the process, then attach the debugger to the process and call bt. 
>> This will give you the current call stack and hopefully some idea where 
>> to look further.
>> 
>> 
>> Regards,
>> 
>> Roland
>> _______________________________________________
>> Boost-users mailing list
>> Boost-users_at_[hidden]
>> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25745829.html
Sent from the Boost - Users mailing list archive at Nabble.com.