#7 sigsegv when playing in despotify clients

[Andy Valencia]

x86 32-bit build with libao and libmpg123. Log in and search OK, sigsegv when I "play 1".
Backtrack indicates snd_ioctl() line 280, it's deref'ing buff->ptr[5] and buff->ptr is NULL.
Bombs in both the ncurses and simple CLI clients.
This is top of SVN as of 1/25/2013.

[CurlyJefferson]

I haven't opened despotify in a while and was curious in making something with the python bindings today, when I noticed this happening; it's immediate every time I try to play a track. Here's exactly what I got from running despotify-simple in gdb:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4b80700 (LWP 4713)]
0x00007ffff77a1b15 in snd_ioctl (ds=0x609fe0, cmd=2, data=0x0, length=0) at sndqueue.c:280
280 if (ds->fifo->lastcmd == SND_CMD_START && (buff->ptr[5] == 6)) {
(gdb) step
[Thread 0x7ffff4b80700 (LWP 4713) exited]
[Thread 0x7ffff59b7700 (LWP 4712) exited]

Hope this helps? I'm not experienced in debugging this kind of thing at all, but hopefully the additional comment will increase visibility...

[Alessio Cecchin]

I compile and run despotify on my Raspberry Pi (ARM) and on my Ubuntu workstation (Quantal 64bit). I obtain the same result, when I try to play a track:

Ouch, I segfaulted. How embarrassing. :-(