Re: [Plib-users] Crash in plibsl

[Alexander R. <a_r...@in...>]

Hi,

Steve Baker wrote:

> I guess the first question is whether your application is corrupting
> something that *SUBSEQUENTLY* kills SL.  The simplest way to prove
> that either way would be to play your MOD file using the sample program.
> 
> Change 'mod_demo.cxx' so that instead of loading "Paravoka.mod", it
> loads your MOD file - and let me know if it still crashes.

This is the file:

alex@annika:/vast1/source/kobayashimaru > dir sounds/big*
-r--r--r--   1 alex     users       58596 Oct 15  1996
sounds/bigjapn2.mod

I copied the file to the examples/src/sl directory as Paravoka.mod, and
tried
it:

alex@annika:/vast1/source/3d/plib/plib-cvs0808/examples/src/sl >
./mod_demo 
Segmentation fault
alex@annika:/vast1/source/3d/plib/plib-cvs0808/examples/src/sl > time
./mod_demo
 
Segmentation fault

real    2m2.278s
user    0m0.070s
sys     0m0.000s
alex@annika:/vast1/source/3d/plib/plib-cvs0808/examples/src/sl > time
./mod_demo
 
Segmentation fault

real    2m2.286s
user    0m0.080s
sys     0m0.000s
alex@annika:/vast1/source/3d/plib/plib-cvs0808/examples/src/sl > time
./mod_demo
 
Segmentation fault

real    2m2.282s
user    0m0.050s
sys     0m0.030s
alex@annika:/vast1/source/3d/plib/plib-cvs0808/examples/src/sl >
./mod_demo 
Segmentation fault


Somehow, it crashes, but no debug printout this time.

> If it does crash - then we are certain the problem isn't in your
> application - and you can rest easy.  Presumably we'd be looking

Phew. Lucky me ;-)

> at either a straight SL
> bug or a corrupted or illegal MOD file -

I suspect an illegal MOD file - it was just lying around, never tested
it
before.

> and a problem that SL is not detecting that corruption and reporting
> it.

Probably.

> We could go on to try to play the MOD file in another MOD player like
> FunkTrackerGOLD (which I use).  If that reports a problem (or crashes

Urks - I don't know if I've got some Tracker lying around.

> or something) then we'll know it's a corrupt MOD file - and we'll have

I can send it to you/ put it in my ftp-space, if you like.

> to chase down SL's error recovery routines to find out why it died after
> complaining instead of just exiting fatally but cleanly or aborting the
> music or something.  Something as simple as changing the existing printf's
> into something more like "Corrupt MOD file - Bye-Bye" - followed by an 'exit'
> will suffice IMHO.

Aeh - no.
You should abort the playing of this mod, maybe try it from the
beginning
(if called as loopMusic()), but you shouldn't abort the hole program if
there's any chance that gameplay can continue without playing the MOD
(or without playing any sounds) or report an error somehow back to the
game that uses sl, but please no exit().

> If the 'mod_demo' crashes - but FunkTracker plays it flawlessly - then
> we have a genuine SL bug and you'll have to send me the MOD file so I
> can debug SL.  The MOD player is horribly complex and I wouldn't wish
> that problem on anyone!

I'll copy it to my ftp-space, directory plib before I send this mail.

> > I am currently using plib from cvs date 8. August 2000
> 
> SL hadn't changed in well over a year - so it shouldn't matter which
> version you have.

Have you thought about playing MIDI-Files? (I know it's very different
in playing
from mods)
I personally would like that better, and I have many MIDI-files around.

> It's by *far* the most stable PLIB component - and I'm pretty suprised
> to find a bug report.

Shove me a virtual glass of champagne :-)

I didn't touch MODs since I dumped my Amiga, and I expect one can
probably
find more corrupt MODs with real bad sound in the net than good ones?

> So, work through the decision tree and tell us which branch you end up in!
> 
>                          Try playing MOD in mod_demo
>                                     / \
>                                    /   \
>                               Works     Crashes
                                          ^^^^^^^

> Another 'gut feeling' is that if it crashes intermittantly then it's MUCH
> more likely to be an application problem than an SL bug.  Interactive

I proably didn't run that mission with that MOD for more that 2min
before,
so the error didn't occur


Alex

-- 
                   Alexander Rawass
          Email: ale...@us...
   Project Homepage: http://kobayashimaru.sourceforge.net
...but some day you'll be a STAR in somebody else's SKY...