Hi, On Sun, Jan 05, 2014 at 10:09:08PM +0000, Manuel A. Fernandez Montecelo wrote: > Hi, > > (Please keep me in CC if you want more input from me). > > > 2014/1/5 Christian T. Steigies <c...@debian.org>: > > Manuel, > > maybe you as the "new" sdl-mixer maintainer have an idea sdl-mixer1.2 can > > not play xm audio files anymore? Perhaps this is an SDL bug? Or is it a > > feature and XM files should be converted? > > > > Christian > > I added modplug support about a year ago. This was motivated by this > change upstream for 2.0.0 version: > > 2.0.0: > Sam Lantinga - Sun Jun 9 14:45:30 PDT 2013 > * Made libmodplug the default MOD player as it is now in the public domain > > > The same support existed in 1.2 since 2009 although disabled, so I > thought that it would be useful to have modplug enabled in 1.2 if it > was the preferred lib for SDL2_mixer:
How did gemdropx play this file then if support was disabled? > 1.2.12: > [...] > Jon Atkins - Sat Nov 14 13:00:18 PST 2009 > * Added support for libmodplug (disabled by default) > > > Also because modplug seems more popular by a far margin: > > > http://qa.debian.org/popcon-graph.php?packages=libmikmod2+libmodplug1&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 > > > So I think that this failure might be because the XM files are now > interpreted by modplug which cannot read the file. > > It would be useful if you install "mikmod" and "modplug-tools" and try > to verify if they both can play the file, or have some problem, etc. mikmod and modplug123 play the XM files just fine. However, modplugplay does not: cts@guido:~/debian/package/gemdropx/gemdropx-0.9/data/sounds>modplugplay 2force.xm opened /dev/dsp for playing 2force.xm [1/1] [207732] Segmentation fault strace ends with this, maybe you can decrypt it: write(1, "opened /dev/dsp for playing 2for"..., 53opened /dev/dsp for playing 2force.xm [1/1] [207732] ) = 53 ioctl(3, SNDCTL_DSP_SETFMT or SOUND_PCM_READ_BITS, 0x7fff18b609e4) = 0 ioctl(3, SNDCTL_DSP_CHANNELS or SOUND_PCM_READ_CHANNELS, 0x7fff18b609e8) = 0 ioctl(3, SNDCTL_DSP_SPEED or SOUND_PCM_READ_RATE, 0x7fff18b609ec) = 0 brk(0xde1000) = 0xde1000 brk(0xe05000) = 0xe05000 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(0, SNDCTL_TMR_START or TCSETS, {B38400 opost isig -icanon -echo ...}) = 0 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig -icanon -echo ...}) = 0 write(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\377\377\377\377"..., 4096) = 4096 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ Segmentation fault > If this is the case, I think that it would be useful to either fix the > XM files (if it's a problem with the format of the file itself, if the > most popular interpreter has problems) or report the bug to ModPlug > (maybe it's more popular but the support for XM is incomplete). modplugplay and modplug123 both come from modplug-tools and use libmodplug. One works, the other does not. So where is the bug? mikmod does not use libmodplug, and works. > Other changes might have caused this, e.g. overflow protection now > enabled for sdl-mixer1.2 getting in the way. Maybe there is an overflow (how can I find out?) which triggers in modplugplay and libsdl-mixer, but not in mikmod and modplug123. But why was this never noticed before? frozen-bubble has only ogg files no xm, so we can not compare with that. I downloaded the first free XM mod that I could find: http://modarchive.org/index.php?request=view_by_moduleid&query=134430 And it plays with mikmod and modplug123, but not in modplugplay: modplugplay boos_lullaby2.xm /dev/dsp (boos_lullaby2.xm): Device or resource busy But the other files give the same message: modplugplay 2force.xm /dev/dsp (2force.xm): Device or resource busy I would say something is broken in modplugplay or libmodplug (which strangely does not trigger in modplug123), a segfault should never happen, even if there were an "overflow" in the XM file. So forward the bug to modplug-tools or libmodplug1? Both maintainers are in Cc, maybe they have an idea. Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
