From: Gottfried N. <Got...@gm...> - 2004-01-19 22:31:13
|
Hi, I tried to compile and run gwc-0.19-10 and gwc-0.19-9. First I tried 0.19-10. On my system the audio playback did not work. I tried play a .wav file: silence. The cursor did not move. No difference between OSS and Alsa. Then I compiled 0.19-9. I can play the .wav file. I tried to declick. It works. I tried to denoise, picked a sound sample, clicked on the denoise button: segmentation fault. In the debugger I found that the segfault occured in denoise.c at line 422. This is really strange. Just for fun, I reduced the size of DENOISE_MAX_FFT to 16384. Now it works. This is even stranger. Could someone please explain what is going on there? My system runs under SuSE Linux 8.2 (glibc 2.3.2, gcc 3.3.1, fftw 2.1.3). The meschach configure script assumes that the current directory is in the PATH. This is not always true. Lines like DEFS="$DEFS -DD_MACHEPS=`macheps`" should be DEFS="$DEFS -DD_MACHEPS=`./macheps`" Thanks, Gottfried |
From: Jeff W. <we...@ya...> - 2004-01-20 02:37:53
|
I think you have other problems with your SuSE setup. I'm just guessing because line 422 in denoise.c for gwc-0.19-9 is the first executable line of code after a *lot* of memory has been allocated from the stack. When you changed the DENOISE_MAX_FFT to 16384, you cut in half the memory needed to hold those arrays. I'm on a Redhat 9.0 system, and my glibc is 2.3.2-27.9, with gcc-3.2.2-5. It's possible what you are seeing is because of the compiler difference, but that's usually the last place to check. For an experiment, you could write a simple C routine that just allocates a lot of memory in local variables, and see if you can reproduce the error. If you change DENOISE_MAX_FFT to 16384 in gwc-0.19-10, do you hear sound? Anybody else have ideas or suggestions for Gottfried? jw Gottfried Necker wrote: > Hi, > > I tried to compile and run gwc-0.19-10 and gwc-0.19-9. First I tried 0.19-10. > On my system the audio playback did not work. I tried play a .wav file: > silence. The cursor did not move. No difference between OSS and Alsa. > > Then I compiled 0.19-9. I can play the .wav file. I tried to declick. It > works. > I tried to denoise, picked a sound sample, clicked on the denoise button: > segmentation fault. In the debugger I found that the segfault occured in > denoise.c at line 422. This is really strange. Just for fun, I reduced the > size of DENOISE_MAX_FFT to 16384. Now it works. This is even stranger. > > Could someone please explain what is going on there? > > My system runs under SuSE Linux 8.2 (glibc 2.3.2, gcc 3.3.1, fftw 2.1.3). > > The meschach configure script assumes that the current directory is in the > PATH. This is not always true. > Lines like > DEFS="$DEFS -DD_MACHEPS=`macheps`" > should be > DEFS="$DEFS -DD_MACHEPS=`./macheps`" > > Thanks, > Gottfried > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: Gottfried N. <Got...@gm...> - 2004-01-20 21:22:24
|
On Tuesday 20 January 2004 03:37, Jeff Welty wrote: > I think you have other problems with your SuSE setup. I'm just guessing > because line 422 in denoise.c for gwc-0.19-9 is the first executable > line of code after a *lot* of memory has been allocated from the stack. > When you changed the DENOISE_MAX_FFT to 16384, you cut in half the > memory needed to hold those arrays. I'm on a Redhat 9.0 system, and my > glibc is 2.3.2-27.9, with gcc-3.2.2-5. It's possible what you are > seeing is because of the compiler difference, but that's usually the > last place to check. I've already checked that. I compiled most of the code with gcc 2.95.3 on the very same system. The problem remains. > > For an experiment, you could write a simple C routine that just > allocates a lot of memory in local variables, and see if you can > reproduce the error. > > If you change DENOISE_MAX_FFT to 16384 in gwc-0.19-10, do you hear sound? Yes, everything seems to work. I can denoise. Gottfried |