Re: Why destroy notify callback inputs wrong?



learfox furry ao net writes:
I have a destroy callback for a gtk window, however when that window
is unref'ed (gtk_widget_unref()) the destroy signal callback is called
but given wrong inputs.

#2  0x807e6c9 in TexBrowserCloseCB (widget=0x8249c40, event=0x816c278, 
    data=0x401f4578) at texbrowsercb.c:1925
... 
As you can see on frame #1 data=0x401f4578, but it should be 0x816c278,
since the signal callback was set to pass the data as tb=0x816c278.


Destroy callbacks have the object as first arg and user data as
second; there's no event. Note that the second arg is 0x816c278.

Havoc




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]