On Mon, 25 Sep 2006, Klaus-M. Klingsporn wrote:
> Am / On Mon, 25 Sep 2006 10:56:30 +0200 (CEST)
> schrieb geiger <[EMAIL PROTECTED]>:
>
> Whow, what a fast reply ...
Yeah, thats Debian :) - a joke, really, seems there you were just lucky.
> > My first guess
> > is that something in your rezound settings is corrupted. Have you
> > used the program before ?
> > Can you try to move your .rezound folder to another place
>
> I just tried it, no change! The .rezound-folder is created newly, when
> I try to start rezound and contains a 0 byte file prsets.dat and a file
> rgistry.dat with the following contents:
>
> "// ReZound program generated data; be careful if modifying. Modify
> ONLY when ReZound is NOT running. Consider making a backup before
> modifying!
>
> AudioOutputMethods={"oss","alsa","jack","portaudio"};"
>
> The files are the same whether I use only "rezound" to call the program
> or "rezound --audio-method=oss"
>
The same here. Except that I do not have a segmentation fault.
> > Another way to debug the problem would be to look a the core-dump.
> > Is there a way I could access that ?
>
> No problem, I put in on my webspace:
>
> wget http://home.tiscali.de/klaumikli1/rezound/core.12294
Thanks, I got it, but it didn't help me as I couldn't see where
it crashed, because rezound is compiled withour debugging information.
I put a rezound version (only the executable) at:
gige.xdv.org/rezound
If you download it to your home and try to start that, maybe we can find
out what happens with that core file.
Nevertheless, it seems that the behaviour of rezound on your machine is
really an exception. Do you have problems with other programs too
(especially with compiling things). This would mean that you have
a hardware problem (faulty memory).
Another cause could be library version, although I doubt that they
have an influence at this early stage of the program startup.
Günter
