On Sat, 2004-10-16 at 12:39, Ben Armstrong wrote: > Today when opening a starter after drawing for a bit, I was asked to > save my drawing; I think I clicked no, but I won't swear to that, and > then Tux Paint crashed (SDL parachute deployed). No core file was > produced, and I was unable to reproduce the problem, performing similar > steps (both answering "yes" and "no" when I was prompted to save).
I'm in a bad way with this bug. It's not easily reproducible and ... > I am nearing the end of my evaluation of 0.9.14 so I can release the > Debian package, and this is the only puzzle that remains. How do we > "catch it in the act"? This is the second time this happened to me. > The first was several days ago. When it happens again, I need to > provide a bit more useful info, but don't know how to do that. Is there > a way we can force Tux Paint to produce a core file when it crashes in > this manner? The Debian package continues to be unreleased. I'd really like to get it into Sarge. If this is the same bug as Koos has encountered (and I suspect it is) then all I can do is wait to see if his debugging effort turns up answers (since his manifestation of the bug at least seems reproducible). I suppose I could attach gdb to a running Tux Paint and *hope* that it crashes. But so far, the crashes are so unreliable, there's no guarantee that would produce results. I'd appreciate it if someone with Debian sid could try my package and induce it to crash under gdb in the same manner as I have reported so we can move towards a solution on this one. Ben -- Ben Armstrong <[EMAIL PROTECTED]> _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
