#1568: crash in 1.3.5-rc2
----------------------+-----------------------------------------------------
Reporter: jth | Owner:
Type: defect | Status: new
Priority: highest | Milestone: 1.3.5
Component: message | Version: devel
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Comment (by erijo):
Unfortunately the latest crash seems to be a locking issue with a user,
not the owner as the first backtrace showed. So the breakpoint is on the
wrong function :(
The breakpoint should be on ICQUser::Lock. But since this function is
called very much it's not very convenient to manually continue every time
the function is called.
Luckily gdb can do it for us. I've attached attachment:backtrace.gdb that
will break every time ICQUser::Lock is called, print a backtrace and then
continue. The output is saved in backtrace.log in the current directory.
Download the file and run
{{{
gdb -command backtrace.gdb --args licq
}}}
and wait until Licq aborts.
Thanks for helping us track this bug down.
--
Ticket URL: <http://trac.licq.org/ticket/1568#comment:9>
Licq <http://trac.licq.org/>
Licq - an instant messaging client for UNIX.
