BUGabundo, the libxml comment wasn't directed at you. http://launchpadlibrarian.net/23818717/gdb-pidgin.85.txt (from BlueT) contains a number of calls in libxml2, for which it would probably be helpful to have those debug symbols.
In general, you don't need to run pidgin inside of gdb constantly. Instead, what you can do is something like: $ cd ~ $ mkdir pidgin-core-dumps and then start Pidgin (always) as: cd ~/pidgin-core-dumps; ulimit -c unlimited; pidgin & When pidgin crashes, it will leave coredumps in that directory, which you can get a backtrace from like: gdb pidgin -c ~/pidgin-core-dumps/core-file -- pidgin crashes with glibc error "double free or corruption" https://bugs.launchpad.net/bugs/184796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
