Re: [Tuxpaint-devel] Kaleidoscope crash

[Caroline F. <car...@go...>]

On 30/11/2007, Caroline Ford <car...@go...> wrote:
> On 30/11/2007, Pere Pujal i Carabantes <pe...@fo...> wrote:
> >
> > El ds 01 de 12 del 2007 a les 00:14 +0100, en/na Pere Pujal i Carabantes
> > va escriure:
> > > El dj 29 de 11 del 2007 a les 07:50 -0800, en/na Bill Kendrick va
> > > escriure:
> > > > Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
> > > > FWIW) when using the new Kaleidoscope tool:
> > > >
> > > >   https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938
> > > >
> > > > Anyone seen this? :(
> > > >
> > > Running with sound works fine, but without sound:
> >
> > BTW magic displace crashes as well without sound.
> >
>
> Running on Ubuntu gutsy without sound I get a crash with the
> kaleidoscope tool when I clicked on a new colour.
>
> I have the following from valgrind:
>
> Process terminating with default action of signal 11 (SIGSEGV)
> ==19239==  Access not within mapped region at address 0x4
> ==19239==    at 0x40F3630: Mix_HaltChannel (mixer.c:829)
> ==19239==    by 0x80597F9: magic_stopsound (in /usr/local/bin/tuxpaint)
> ==19239==    by 0x7E39D19: kalidescope_release (in
> /usr/local/lib/tuxpaint/plugins/kalidescope.so)
> ==19239==    by 0x8065B3C: main (in /usr/local/bin/tuxpaint)
>
> I have the full trace I can send as I've no real clue on how to read
> valgrind traces.
>
> Caroline
>

Run the same under gdb. It crashed at the same point.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222666560 (LWP 19326)]
0xb7e02630 in Mix_HaltChannel (which=0) at mixer.c:829
829	mixer.c: No such file or directory.
	in mixer.c

I've attached the trace but I don't know how to get debug symbols on
tuxpaint, but I have installed debug symbols in all sdl etc.

Caroline