[swift-users] Segfault when joining MUC

[Kevin Smith]

On Tue, Aug 30, 2011 at 8:40 PM, Mazhe <vmazhe at gmail.com> wrote:
> 2011/8/29 Tobias Markmann <tmarkmann at googlemail.com>:
>> Mind telling us which ejabberd server that is? If you don't want to
>> tell, do you at least know the version of ejabberd running there?
>> Are you able to reproduce this crash repeatedly?
>> "I'm using the latest git version." <-- Which version exactly? (You
>> can find out via "git log -n 1")
>
> For some reason, I cannot access activity[0] in gdb, here is activity
> however that seems to be empty if I'm not mistaken (so it would
> explain my activity[0] problem)?
> (gdb) print activity
> $1 = {<std::_Vector_base<std::basic_string<char,
> std::char_traits<char>, std::allocator<char>
>>,std::allocator<std::basic_string<char, std::char_traits<char>,
> std::allocator<char> > > >> = {
>    _M_impl = {<std::allocator<std::basic_string<char,
> std::char_traits<char>, std::allocator<char> > >> =
> {<__gnu_cxx::new_allocator<std::basic_string<char,
> std::char_traits<char>, std::allocator<char> > >> = {<No data
> fields>}, <No data fields>}, _M_start = 0x0, _M_finish = 0x0,
>      _M_end_of_storage = 0x0}}, <No data fields>}

Yep, right on the money.

activity should never be empty, it should always have a length of at
least one, even when boost::split is passed the empty string, as it
was here.

I would guess you're being hit by
https://svn.boost.org/trac/boost/ticket/4751 - is it possible that
you're compiling with a system Boost of an afflicted version? If so,
compiling with the (older) bundled boost may help.

/K