Re: Timer problems.

[Dylan Griffiths <dylang+gtk_devel thock com>]

Owen Taylor wrote:
> 
> Remember, if you make mistakes in handling lists in your program,
> and for instance, free a list node and keep on using it, then
> GTK+/GLib may get that node from the free list. Then when
> GLib manipulates the node, your data structures will become
> corrupted.

I spent 2 hours tracing this around.  I malloc the initial node of the
linked list during startup, and do not free it in the entire source code
(feel free to grep for a free).  When I was stepping through the
timercallbacks in gdb, the memory did not self corrupt.  However, when I
"continue"ed, that's when corruption occured.

Baring hardware problems, I think it's either something in the gtk timer or
gtk label overflowing.  I would greatly appreciate it if you could run the
program there and say YES or NO.  I have checked over my code for leaks,
etc.  But if you can find me being a bonehead in the code, I will go off and
fix it myself and not speak of this again :^)
 
> This is almost certainly what is going on. There are quite
> a few examples of very complex programs that use lists and
> the GLib main loop that don't hit the problem, so I would
> really have to suspect something in your code.

-- 
    www.kuro5hin.org -- more than a state of mind.