|
|
I'm working on a private branch of kyzis (http://www.yzis.org) and I've come
across a strange crash in Qt. The backtrace only contains Qt code and is
100% reproducible The crash occurs with both debian's Qt 3.3 and KDE's
qt-copy. It always happens when trying to allocate 513 bytes for a
QCString. I was wondering if anybody could give me some hints for
debugging this one. I can post my yzis snapshot somewhere if that helps.
I've been bashing my head against it for a couple days now. Thanks.
#0 0xb66ae2cd in malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
#1 0xb66adb1d in _int_malloc () from /lib/tls/i686/cmov/libc.so.6
#2 0xb66ace83 in malloc () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7189929 in QGArray (this=0xbffff140, size=513) at
tools/qgarray.cpp:146
#4 0xb717e66e in QMemArray (this=0xbffff140, size=513) at qmemarray.h:59
#5 0xb717babe in QCString (this=0xbffff140, size=513)
at tools/qcstring.cpp:679
#6 0xb6db91a1 in QETWidget::translateKeyEventInternal (this=0x82fcff0,
event=0xbffff630, count=@0xbffff324, text=@0xbffff300,
state=@0xbffff320,
ascii=@0xbffff31f, code=@0xbffff328, type=@0xbffff314, willRepeat=false)
at kernel/qapplication_x11.cpp:4999
#7 0xb6db9c81 in QETWidget::translateKeyEvent (this=0x82fcff0,
event=0xbffff630, grab=false) at kernel/qapplication_x11.cpp:5345
#8 0xb6db631d in QApplication::x11ProcessEvent (this=0xbffff7c0,
event=0xbffff630) at kernel/qapplication_x11.cpp:3482
#9 0xb6dd0b9f in QEventLoop::processEvents (this=0x8117d88, flags=4)
at kernel/qeventloop_x11.cpp:192
#10 0xb6e3ed21 in QEventLoop::enterLoop (this=0x8117d88)
at kernel/qeventloop.cpp:198
#11 0xb6e3ec3a in QEventLoop::exec (this=0x8117d88)
at kernel/qeventloop.cpp:145
#12 0xb6e2a861 in QApplication::exec (this=0xbffff7c0)
at kernel/qapplication.cpp:2758
#13 0x08071585 in main (argc=1, argv=0xbffff964) at main.cpp:117
--
Craig Howard
|
|