Re: [Tuxpaint-dev] Tux Paint Segfault if unable to print
On Sat, Jan 22, 2005 at 09:14:39PM -0500, Albert Cahalan wrote: So, I take it that the various other crashing problems are gone now? How are things with stamps and fonts? Sadly, no. Last I tried, I let it sit for a min. or so w/o hitting the 'Text' tool. Then, when I hit it, I got a short font-related mesg. on stdout and Tux Paint crashed immediately. Got 0 bytes with families. ... where ### was a large number (in the 10s of thousands range?) I'm away from home ATM, so cannot examine further. -bill! (via zaurus) ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] Tux Paint Segfault if unable to print
On Sun, 2005-01-23 at 03:21, Bill Kendrick wrote: On Sat, Jan 22, 2005 at 09:14:39PM -0500, Albert Cahalan wrote: So, I take it that the various other crashing problems are gone now? How are things with stamps and fonts? Sadly, no. Last I tried, I let it sit for a min. or so w/o hitting the 'Text' tool. Then, when I hit it, I got a short font-related mesg. on stdout and Tux Paint crashed immediately. Got 0 bytes with families. ... where ### was a large number (in the 10s of thousands range?) The number is bogus, because it was never received. (you got 0 bytes) After getting 0 bytes, crashing is totally expected. This should never happen; Tux Paint would already have exited if default_font were not available. You should have also seen this: printf(Sending %u bytes with %u families.\n, size, num_font_families); Did you? (it's really important to be sure about this) If you saw that, there is an IO problem. If you didn't see that, the child crashed. ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
Re: [Tuxpaint-dev] Tux Paint Segfault if unable to print
On Sun, Jan 23, 2005 at 11:51:44AM -0500, Albert Cahalan wrote: You should have also seen this: printf(Sending %u bytes with %u families.\n, size, num_font_families); Did you? (it's really important to be sure about this) Nope! If you saw that, there is an IO problem. If you didn't see that, the child crashed. It must be the latter. It went like this: $ tuxpaint Start-up time: 4.177 ... I wait about 1-2 minutes, then click 'Text' ... Got 0 bytes with 62292 families. Segmentation fault $ *boom!* :^) Again, I haven't changed fonts recently, and for a while (before the threading change), it /was/ working... just took forever to start up :) -bill! [EMAIL PROTECTED] April shower bring Kompressor power! http://newbreedsoftware.com/ ___ Tuxpaint-dev mailing list Tuxpaint-dev@tux4kids.net http://tux4kids.net/mailman/listinfo/tuxpaint-dev
