On Jul/04, Nicolas Évrard wrote:
Now minbif do not crash but I've got those messages in a request
window:
08:24 <request> :: Error Reading blist.xml ::
08:24 <request> An error was encountered reading your buddy list.
The file has not been loaded, and the old file has been
renamed to /var/lib/minbif/users/nicoe/blist.xml~.
And in the status window:
08:19 !nutellux.dyndns.org Minbif-IRCd initialized, please go on
08:19 ::: ERROR Closing Link: Incorrect credentials
08:19 ::: Connection lost to localhost
But I never changed my credentials.
maybe the conf file got corrupted somehow ?
I will move /var/lib/minbif/users/nicoe to something else to try with
a brand new setup.
I indeed have a core file in minbif/users but trying to get the
backtrace gave me no stack:
root@mnms:/var/lib/minbif/users# gdb core
GNU gdb (GDB) 7.2-debian
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
"/var/lib/minbif/users/core": not in executable format: Format de fichier non
reconnu
(gdb) bt
No stack.
You'll need to run "gdb minbif core" if I'm not mistaken.
You were right, here is the backtrace:
(gdb) bt
#0 0x00000000004902f9 in irc::Server::addNick(irc::Nick*) ()
#1 0x000000000046e336 in irc::IRC::addNick(irc::Nick*) ()
#2 0x000000000045d496 in
im::Conversation::recvMessage(std::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
std::basic_string<char, std::char_traits<char>, std::allocator<char>
>, bool) ()
>#3 0x000000000045db05 in
>im::Conversation::write_conv(_PurpleConversation*, char const*, char
>const*, char const*, PurpleMessageFlags, long) ()
>#4 0x00007fdaa2a21881 in purple_conversation_write () from
>/usr/lib/libpurple.so.0
>#5 0x00007fdaa2a546bf in serv_got_im () from /usr/lib/libpurple.so.0
>#6 0x00007fda99de9be9 in ?? () from /usr/lib/purple-2/libjabber.so.0
>#7 0x00007fda99deacc8 in jabber_message_parse () from
>/usr/lib/purple-2/libjabber.so.0
>#8 0x00007fda99ddfdfb in jabber_process_packet () from
>/usr/lib/purple-2/libjabber.so.0
>#9 0x00007fda99decca7 in ?? () from /usr/lib/purple-2/libjabber.so.0
>#10 0x00007fda9fc4da93 in ?? () from /usr/lib/libxml2.so.2
>#11 0x00007fda9fc54930 in ?? () from /usr/lib/libxml2.so.2
>#12 0x00007fda9fc560a8 in xmlParseChunk () from /usr/lib/libxml2.so.2
>#13 0x00007fda99decd1d in jabber_parser_process () from
>/usr/lib/purple-2/libjabber.so.0
>#14 0x00007fda99ddbb12 in ?? () from /usr/lib/purple-2/libjabber.so.0
>#15 0x000000000043153c in ?? ()
>#16 0x00007fdaa27144a3 in g_main_context_dispatch () from
>/lib/libglib-2.0.so.0
>#17 0x00007fdaa2714c80 in ?? () from /lib/libglib-2.0.so.0
>#18 0x00007fdaa27152f2 in g_main_loop_run () from
>/lib/libglib-2.0.so.0
>#19 0x000000000042a1a8 in Minbif::main(int, char**) ()
>#20 0x000000000042d900 in main ()
I'm tagging "unreproducible" and downgrading to normal since it
doesn't seem to be a crash... I'll update those as needed, as we
continue investigating.
Ok. But this bug (even it is not reproducible) has a major effect on
the usability of the package (at least for me), so I think its level
should be 'important'.
--
(°> Nicolas Évrard
( ) Liège
`¯
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
