Re: [Bug-freedink] Potential bug in FreeDink

[Sylvain Beucler]

Hi!

> I got another segfault - the result of pressing an arrow key (and
> possibly other keys) after the credits in PQ. While quite harmless
> in this case since it is after the game has finished, it might be
> due to some bug that could potentially cause problems in other
> DMODs, so I thought I should let you know about it.

Thanks for the report and the savegames.

It's a FreeDink issue this time, where the game didn't quit cleanly
when the DinkC kill_game() command is used, and so the sound system
was still used after it was unloaded, hence the segfault.

I reimplemented it differently and more cleanly:
http://git.savannah.gnu.org/gitweb/?p=freedink.git;a=commitdiff;h=14e52a2a757723e57d269d352a02c164cb992b2d


> One thing I forgot to mention - I have some problems with crackling  
> sounds. This happens when I'm not running the game if I turn up the  
> volume too high on my integrated sound (VIA Technologies Inc. VT1720/24  
> [Envy24PT/HT] according to lspci) but in FreeDink it happens even if I  
> set the sound to quite low.

Hmmm, this one is more difficult to track. Does it happen
continuously?

I have a similar problem on an old laptop (with an Intel AC'97) where
when Dink is very near a save machine, there's a crackling noise. I
haven't figured out what's wrong yet.

Can you send me your 'Audio hardware info' line from when the game
starts? Mine looks like this:
Audio hardware info: frequency=22050Hz format=S16LSB channels=2 opened=1 times

Thanks,

-- 
Sylvain