Greetings people,
This may be an old problem, long since resolved but if you would indulge
me ...
I am currently experimenting with replacing cairo with clutter on the
gtkpod project. At the moment, I have successfully brought up a
ClutterEmbed widget. The widget displays correctly with a black
background as required. However, I keep receiving the BadWindow error
upon closing the application:
The program
'/home/phantomjinx/programming/cpp/gtkpod/src/.libs/lt-gtkpod' received
an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8414 error_code 3 request_code 10 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
Having tried to run it with gdb and the --sync option still does not
return anything useful. Can anyone give me some pointers that I could
try to get further information on what may be causing the error please?
Thanks and Regards
Paul (a.k.a. phantomjinx)
his GDB was configured as "i586-mandriva-linux-gnu"...
(gdb) run --sync
Starting program:
/home/phantomjinx/programming/cpp/gtkpod/src/.libs/lt-gtkpod --sync
[Thread debugging using libthread_db enabled]
[New Thread 0xb4f1fa70 (LWP 17645)]
Detaching after fork from child process 17680.
[New Thread 0xb074db70 (LWP 17681)]
Number of active plugins: 12
[New Thread 0xaa4ddb70 (LWP 17687)]
[Thread 0xaa4ddb70 (LWP 17687) exited]
The program
'/home/phantomjinx/programming/cpp/gtkpod/src/.libs/lt-gtkpod' received
an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 19655 error_code 3 request_code 10 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
[Thread 0xb074db70 (LWP 17681) exited]
Program exited with code 01.
(gdb)
(gdb)
(gdb) bt
No stack.
(gdb)
_______________________________________________
clutter-app-devel-list mailing list
[email protected]
http://lists.clutter-project.org/listinfo/clutter-app-devel-list
