Re: Gdk segfault messages

[Conrad Steenberg <conrad srl caltech edu>]

Hi

Thanks for your reply.


> I can not reproduce this problem myself.  Are you sure you dont have
> any older gtk+ libraries installed on the system lying around or at
> the time you compiled the code?
> 
> Miguel.
> 

I'm positive: I recompiled gtk and glib inserted a debugging message in
gtk_selection_retrieval_report in gtkselection.c (around line 1262). The
debug message was printed.

The error also occurs when the example in examples/selection/gettargets is
ran. In this prog the segv occurs first when selection_data->length is
accessed. The pointer selection_data (of type GtkSelectionData) is not 0,
and is the same as is sent when the "selection_received" signal is emitted
in gtkselection.c. My guess is that the memory is somehow corrupted between
the call to gtk_signal_emit_by_name and the actual call to the signal
handler.

This is the debug message in gtkselection.c:
'selection_received' signal about to be emitted...data=1ffff250
data->length=48

In the example gettargets.c the following is then printed:
sel_recv: selection_data=1ffff250
Gdk-Message: 
** ERROR **: sigsegv caught

(No it doesn't make sense to me either ;-) I don't know if this may be a
64-bitness issue with the alpha.

Conrad

Ps. The X server is XF86SVGA-3.3.2.1-18 (newest update for redhat 5.1, in
case I remember the version number wrong) on a Matrox M-II. I tried both
gcc-2.8.1 and egcs-1.02, without success.