Re: [gtk-list] Re: gtk--: Really weird thing!!

[Tero Pulkkinen <terop students cc tut fi>]

Oliver Freyd <freyd@uni-muenster.de> writes:
> This is what gdb says:
> 
> Signal_proxy0<void, Gtk_Widget>::operator() (this=0x2de) at
> /usr/local/include/gtk--sig.h:1191
> (xxgdb) print sender->gtkobject
> Cannot access memory at address 0x2e2.
> (xxgdb) print signal_name
> Cannot access memory at address 0x2de.
> (xxgdb) step

cut/paste me what "where"-command prints. that helps quite much more.

> Program received signal SIGSEGV, Segmentation fault.
> 0x8049f5a in Signal_proxy0<void, Gtk_Widget>::operator() (this=0x2de) at
> /usr/local/include/gtk--
> sig.h:1191 

Seems the this pointer of signal_proxy is bad.


> class ColorButton : public Gtk_Button {
> public:
>   ColorButton(gchar * label):Gtk_Button(){
>     GdkWindow * win = GTK_WIDGET(gtkobject)->window;

This window -variable was changed in 0.99.4 and has caused quite many
sigsegv's. I think its not updated until the widget has been shown to
screen anymore. (i.e. it needs to be in the screen before you can do
this)

I couldnt test the programs yet (no X11 here), but that looks a good
ccandidate of what new problems people have with 0.99.4.

-- 
-- Tero Pulkkinen -- terop@modeemi.cs.tut.fi --