Re: Debugging propagated events

2016-11-29 Thread zahlenmeer
I added some logic and after that I got a warning that there is a mismatch between cairo_save and cairo_restore. So I fixed that and I got it working. The cairo logic was faulty all the time but only some new lines of code triggered that warning. So I guess I was just lucky that I stopped

Re: Debugging propagated events

2016-11-28 Thread Jim Charlton
In Gtkmm (C++) you can overload the on_draw() function with your own. This might give you a foothold in the on_draw() routine that is called after a redraw event occurs. I guess in GTK you would have to connect a callback function to the "draw" signal. Might help.?? jim... On 2016-11-28

Re: Debugging propagated events

2016-11-28 Thread Alfonso Arbona Gimeno
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, zahlenm...@gmx.de wrote: >For a custom widget I have a

Re: Debugging propagated events

2016-11-28 Thread zahlenmeer
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

Debugging propagated events

2016-11-28 Thread zahlenmeer
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