[kaffe] Paths problems & awt-qt problems
Fabien Renaud
renaud at nentec.de
Tue Jul 6 02:06:34 PDT 2004
Hello,
It´s the continuation of my problem with a better name :)
So I resume everything :
My configuration :
- Kaffe HEAD
- ARM Machine
- QTE-2.3.4
My goal :
Run awt with qt without problem (hum)
My problem :
When I click on a widget which displays a window I have SOMETIMES a
problem after window destruction : I cannot open another window unless I
resize the main screen.
I have always this message :
wndCreateWindow
QWidget (unnamed): deleted while being painted
QPaintDevice: Cannot destroy paint device that is being painted
getWidth()=-1 producer=java.awt.ImageNativeProducer at 288798 <http://kaffe.org/cgi-bin/mailman/listinfo/kaffe>
If I set a breakpoint on QWidget::~QWidget :
Breakpoint 1, QWidget::~QWidget() (this=0x0, __in_chrg=43168)
at kernel/qwidget.cpp:750
750 in kernel/qwidget.cpp
(gdb) where
#0 QWidget::~QWidget() (this=0x0, __in_chrg=43168) at
kernel/qwidget.cpp:750
#1 0x408137dc in QFrame::~QFrame() () at qasciidict.h:63
#2 0x40952bd4 in QWidget::close(bool) (this=0x40e18ac0, alsoDelete=true)
at kernel/qwidget.cpp:3616
#3 0x406746c0 in Java_java_awt_Toolkit_wndDestroyWindow (env=0x284b8c,
clazz=0x2165dc, wnd=0x40e18ac0) at wnd.cc:424
#4 0x400cdb04 in ffi_call_SYSV () at ../libffi/src/arm/sysv.S:85
#5 0x400cded8 in ffi_call (cif=0xbf3fd5f8,
fn=0x40674504 <Java_java_awt_Toolkit_wndDestroyWindow>,
rvalue=0xbf3ff5e4,
avalue=0xbf3fd5c0) at ../libffi/src/arm/ffi.c:167
-> Ok
When I receive a segfault after window destruction :
Program received signal SIGSEGV, Segmentation fault.
0x4007d170 in runVirtualMachine (meth=0x2b00fc, lcl=0xbf3fe248,
sp=0xbf3fe2a0,
npc=43, retval=0xbf3fe8e4, mjbuf=0xbf3fe338, thread_data=0x284b8c)
at kaffe.def:2452
2452 kaffe.def: No such file or directory.
in kaffe.def
Current language: auto; currently c
(gdb) where
#0 0x4007d170 in runVirtualMachine (meth=0x2b00fc, lcl=0xbf3fe248,
sp=0xbf3fe2a0, npc=43, retval=0xbf3fe8e4, mjbuf=0xbf3fe338,
thread_data=0x284b8c) at kaffe.def:2452
#1 0x40079080 in virtualMachine (meth=0x2b00fc, arg=0xbf3fe578,
retval=0xbf3fe8e4, thread_data=0x284b8c) at machine.c:228
#2 0x4006a92c in callMethodV (meth=0x2b00fc, func=0x2b00fc, obj=0x0,
args=0xbf3fe960, ret=0xbf3fe8e4) at support.c:850
#3 0x4008abd4 in KaffeJNI_CallStaticObjectMethodV (env=0x284b8c,
cls=0x2aea3c, meth=0x2b00fc, args=0xbf3fe94c) at jni-callmethod.c:1220
#4 0x40677758 in JNIEnv_::CallStaticObjectMethod(void*, void*, ...) (
this=0x284b8c, a=0x2aea3c, b=0x2b00fc) at jni_cpp.h:631
#5 0x40676564 in processEvent(JNIEnv_*, _Toolkit*, QEvent*, int) (
env=0x284b8c, X=0x40688d18, event=0x40ea3ec8, index=18) at evt.cc:829
#6 0x406768c0 in Java_java_awt_Toolkit_evtGetNextEvent (env=0x284b8c,
clazz=0x2165dc) at evt.cc:877
#7 0x400cdb04 in ffi_call_SYSV () at ../libffi/src/arm/sysv.S:85
#8 0x400cded8 in ffi_call (cif=0xbf3fea88,
fn=0x40676820 <Java_java_awt_Toolkit_evtGetNextEvent>,
rvalue=0xbf3ff5e4,
avalue=0xbf3fea58) at ../libffi/src/arm/ffi.c:167
Well I have no more informations. If I can do something to give you more
informations, please ask me.
I´d like to debug with jdb but I have a little problem. It wants
kaffe-bin from the my native path. I set KAFFEHOME but that does nothing.
Did I forget something ?
Cheers,
Fabien
More information about the kaffe
mailing list