Thread: [ReZound-users] Re: More on Rezound bug 282002
Status: Beta
Brought to you by:
ddurham
From: Geiger G. <ge...@ma...> - 2005-04-27 11:14:34
|
Hi Dave, Thanks for the additional info. I am forwarding this to the rezound list, but I doubt that we will find a solution soon, as these things seem to be really hard to debug and reproduce. Well, lets hope it goes away by itself :) Anyhow, if someone on the rezound list has more input on this. It might also be a Debian kernel related problem, as it seems that this doesn't occur on other distros ... Clueless Guenter On Thu, Apr 21, 2005 at 01:25:50PM -0400, Dave Maxwell wrote: > I'm having a bit of trouble with reportbug so I just try the direct > approach. I've learned more about the rezound's shuttle freezing on > backwards playback. I have Rezound installed on three machines. All are > P-IVs. Two have HT enabled and one is does not have hyperthreading. The > bug only occurs on HT machines running SMP kernels. The non-HT machine > runs Rezound correctly. The HT machines also run it correctly when HT is > disabled. I don't know what the behaivor is on machines that actually > have dual processors. > > I also built Rezound from the upstream source. The problem still occurs > absent Debian patches to Rezound itself. > > Cheers! > > Dave Maxwell > Technician > Big Walnut Local Schools > > |
From: Davy D. <ddu...@da...> - 2005-04-27 15:32:30
|
If I had to guess: 1) I've got a race condition in the code somewhere that only occurs on multiprocessor machines 2) glibc/kernel has a bug in mutexes that only occurs on multiprocessor machines A possible third option is that FOX or my use of FOX has an issue. I've been suspecting it for some time, but it's still not conclusive. I've got this bug that either only I can produce or no one else has encountered. Basically if you hit 'a' to play, then 'ctrl-a' to select all, then immediately follow that with an other 'a' (any maybe an 's' to stop there in between somewhere) the GUI will freeze (but it continued to play and usually unfreezes when playing stops at end-of-track). Now here's the weird part: I've abstracted mutexes into a class, so I have one point of control for dealing with all mutexes in the application. I added some debugging print statements when a mutex gets locked and then they're unlocked, along with a counter that gets incremented and decremented when it's locked and unlocked to see if it ever says that the mutex was locked twice. Well when I get this condition I noticed that one of the mutex is getting locked twice! I definate no-no for correctly working mutexes. I do however need to make sure that the same thread didn't lock it twice which may be allowed (but this behavior can be disabled with a flag I think) This is the bug that is holding up the next release.. but it's been there for some time apparently and other's haven't reported it, but it's possibly related to the shuttle freeze problem. In both situation's it's the GUI that becomes unresponsive (because it's waiting on a mutex to lock which is never going to for whatever reason). Oh and gdb has not been the best help in all this and I'm not sure why about that either. Just to let you know.. -- Davy Geiger Guenter wrote: >Hi Dave, > >Thanks for the additional info. I am forwarding this to the rezound >list, but I doubt that we will find a solution soon, as these >things seem to be really hard to debug and reproduce. Well, lets >hope it goes away by itself :) >Anyhow, if someone on the rezound list has more input on this. >It might also be a Debian kernel related problem, as it seems that >this doesn't occur on other distros ... > >Clueless > >Guenter > > >On Thu, Apr 21, 2005 at 01:25:50PM -0400, Dave Maxwell wrote: > > >>I'm having a bit of trouble with reportbug so I just try the direct >>approach. I've learned more about the rezound's shuttle freezing on >>backwards playback. I have Rezound installed on three machines. All are >>P-IVs. Two have HT enabled and one is does not have hyperthreading. The >>bug only occurs on HT machines running SMP kernels. The non-HT machine >>runs Rezound correctly. The HT machines also run it correctly when HT is >>disabled. I don't know what the behaivor is on machines that actually >>have dual processors. >> >>I also built Rezound from the upstream source. The problem still occurs >>absent Debian patches to Rezound itself. >> >>Cheers! >> >>Dave Maxwell >>Technician >>Big Walnut Local Schools >> >> >> >> > > >------------------------------------------------------- >SF.Net email is sponsored by: Tell us your software development plans! >Take this survey and enter to win a one-year sub to SourceForge.net >Plus IDC's 2005 look-ahead and a copy of this survey >Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix >------------------------------------------------------- >ReZound-users mailing list >ReZ...@li... >Subscribe/Unsubscribe and change options >https://lists.sourceforge.net/lists/listinfo/rezound-users >ReZound-users mailing list archive >http://sourceforge.net/mailarchive/forum.php?forum=rezound-users > > |