Re: Debugging propagated events

[zahlenmeer gmx de]

This was one of the first things I did. Debug compilation option, debug
CFLAGS, no stripping - without a change. The backtrace only shows 3
lines, my draw function and two from libc.
The faulty address is not null. But the segfault happens after the
return where all local variables are no longer in scope, and the
addresses of the widget and the cairo context are valid.

On 11/29/16 00:44, Alfonso Arbona Gimeno wrote:
> Hi,
>
> Why don't you link against the debug version of the library so that it
> shows you the complete stack?
> It will give you some extra clues on why the segfault is happening.
>
> Regards,
> Alfonso Arbona
>
> On November 29, 2016 6:17:05 AM GMT+09:00, zahlenmeer gmx de wrote:
>
>     For a custom widget I have a draw function. I do some drawing there and
>     when I am finished I return FALSE to let the parent draw. Immediately
>     after the return statement I get a segfault. gdb's backtrace only shows
>     my draw function and an address I cannot associate to any object.
>     Are there some general tricks how to debug such errors?
>
>     Kind regards
>     ------------------------------------------------------------------------
>
>     gtk-app-devel-list mailing list
>     gtk-app-devel-list gnome org
>     https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list