[Gnash] Re: gnash testing

[Jens Petersen]

Jens Petersen wrote:
> For me the client from current anoncvs head runs ok under FC4 but not on 
> FC5: I noticed Fedora Extras 4 has gtkglext 1.0 whereas Extras 5 has 
> 1.2, but I don't know if that is the cause of the crash I see under FC5 

Here is a little more information from gdb for the crash under FC5 
with gtkglext-1.2:

$ gdb gnash
(gdb) set args --sync some.swf
(gdb) b gtk_container_add
(gdb) r
(gdb) c 10
(gdb) bt
#0  IA__gtk_container_add (container=0x551020, widget=0x5554b0)
    at gtkcontainer.c:948
#1  0x00000000004045fd in main (argc=2, argv=0x7fffffac9898) at 
gnash.cpp:538
(gdb) n 10
IA__gtk_container_add (container=0x551020, widget=0x5554b0)
    at gtkcontainer.c:963
963       g_signal_emit (container, container_signals[ADD], 0, widget);
(gdb) s
0x000000315131c4e0 in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0
(gdb) bt
#0  0x000000315131c4e0 in g_signal_emit () from 
/usr/lib64/libgobject-2.0.so.0
#1  0x00000000004045fd in main (argc=2, argv=0x7fffff8779b8) at 
gnash.cpp:538
(gdb) s
Single stepping until exit from function g_signal_emit,
which has no line number information.
The program 'gnash' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 234 error_code 154 request_code 143 minor_code 5)
  (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.)

Program exited with code 01.


Perhaps that will help a little to pinpoint the problem?

Jens