Re: [Monotone-devel] Re: Bug#404616: monotone: Segmentation fault

[Zack Weinberg]

> (gdb) bt
> #0  0x0fe35ecc in __dynamic_cast () from /usr/lib/libstdc++.so.6
> #1  0x100c1ef0 in std::out_of_range::~out_of_range ()
> #2  0x10209214 in boost::detail::shared_count::~shared_count ()
> #3  0x1012a674 in boost::gregorian::bad_month::~bad_month ()
> #4  0x1012b060 in boost::gregorian::bad_month::~bad_month ()
> #5  0x1012b27c in boost::gregorian::bad_month::~bad_month ()
> #6  0x100f6ed8 in std::out_of_range::~out_of_range ()
> #7  0x100f70e8 in std::out_of_range::~out_of_range ()
> #8  0x100f7644 in std::out_of_range::~out_of_range ()
> #9  0x100b7304 in std::out_of_range::~out_of_range ()
> #10 0x1006f78c in std::_Rb_tree<std::string, std::pair<std::string const, unsigned int>, 
> std::_Select1st<std::pair<std::string const, unsigned int> >, std::less<std::string>, 
> std::allocator<std::pair<std::string const, unsigned int> > >::_M_erase ()
> #11 0x102bcbec in std::vector<int, std::allocator<int> >::~vector ()
> #12 0x102befc8 in std::vector<int, std::allocator<int> >::~vector ()
> #13 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6
> #14 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6
> #15 0x0fb49994 in __libc_init_first () from /lib/tls/libc.so.6
> Previous frame inner to this frame (corrupt stack?)
>
> which would seem to imply the stack is corrupt, and very possibly
> meaningless.

That's a completely implausible stacktrace, too, so I think you're
right.  Things to try at this point:

1) Make absolutely sure that the Boost libraries are compiled with the
same version of GCC as Monotone itself.  This is the #1 cause of
inexplicable segfaults.

2) Run the crashing command under valgrind - valgrind does support PPC
now, I believe - and get us a backtrace from that.

zw