** Changed in: pidgin (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: pidgin (Ubuntu)
Status: Fix Committed => Fix Released
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/357868
You received this bug notification because you are a member of Ubuntu
Bugs
Thanks. Marking fixed.
** Changed in: pidgin (Ubuntu)
Status: Incomplete => Fix Released
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/357868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
Its a long time since it crashed.. so i dont think the problem exist any
more.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/357868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
do you still get the issue in jaunty?
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/357868
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.co
you just need to type "run" on the gdb command
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/357868
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.
Backtrack page is very bad written for newbi !
When you have this in terminal :
(gdb)
You need to do this :
(gdb) handle SIG33 pass nostop noprint
write : "handle SIG33 pass nostop noprint" and do enter
same for :
(gdb) set pagination 0
and finally :
(gdb) run /usr/bin/pidgin
or
(gdb) run
I tried to follow the instructions to do a backtrace but i cant get it
to work.. dont know what i do wrong.. please help..
u...@ulha-laptop:~$ gdb /usr/bin/pidgin 2>&1 | tee gdb-pidgin.txt
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or lat
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
