Can you try to get a backtrace of this crash by following the directions
here: http://wiki.debian.net/?HowToGetABacktrace
If you don't have enough time to recompile gaim, you can just try getting
a backtrace without debugging by following the directions starting at the
Now run your program as
On Thu, Aug 04, 2005 at 01:27:39PM -0400, Ari Pollak wrote:
Can you try to get a backtrace of this crash by following the directions
here: http://wiki.debian.net/?HowToGetABacktrace
If you don't have enough time to recompile gaim, you can just try getting
a backtrace without debugging by
On Thu, Aug 04, 2005 at 02:37:59PM -0400, Ari Pollak wrote:
Hm, did you set MALLOC_DEBUG_=2 when running gdb/gaim? If so, it looks
like I'm going to need a full backtrace with debugging symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1219641216
Yup, Debian's gaim currently contains up to revision 1.60.2.3 of ssi.c.
This was the first thing I patched when 1.4.0 came out because I couldn't
log on to AIM :)
Luke Schierer wrote:
Do you all have the patch currently in cvs that fixes problems with
some (but not most) aim screennames? I do
Do you all have the patch currently in cvs that fixes problems with
some (but not most) aim screennames? I do not know if it was sent to
to the packagers or not. it seems only some screennames are effected
at all, users with such screennames report that the problem is
isolatable to a single aim
Package: gaim
Version: 1:1.4.0-3
Severity: grave
Justification: renders package unusable
scar: BOS rights: Max permit = 350 / Max deny = 350
server: allowing NOP
oscar: buddy list loaded
oscar: ssi rights: max type 0x=700, max type 0x0001=61, max type
0x0002=350, max type 0x0003=350, max
6 matches
Mail list logo
