>>> Did you try to increase the stack size? LAME 3.8x allocates local stack
>>> space for the GTK variables even if you don't use GTK (some #ifdef are
>>> gone) and this might lead to your problems. I've set the stack size of
>>> 512 kB and LAME works rock steady on my PPC Mac...
>>Hmm... that's something that I haven't thought of carefully enough. I have
>>used the stack size of 1 meg and that should be enough and I know that
>>m68k side uses that amount of stack but I really don't know whether the
>>startup code for PPC programs uses that stack size or something else (a
>>predefined value, maybe?)... and I don't know how to easily change the
>>stack size on PPC and AmigaOS. I think there are some PPC Amiga
>>programmers here as well so I'm interested in knowing how to do that.
>>Usually the compiler (SAS/C at least) on m68k side can automatically check
>>and/or increase the stack size on the fly, if required and configured. But
>>I don't know if this works on PPC side or not. Anyone who knows better?
>
>There is no easy way to change the stack size in the code...
>
>The only way is to set the shell-stack before running the program .. oh, and
>btw, LAME has never used more than 300k here, and 100k is usually safe...
>
>
You dont need to make stack size that big. I got it working w/ 32k stack
size. Just changed some function locals to be static, e.g. static int
array[BIGNUMBER];
Dmitry
--
Dmitry Boldyrev
Subband Software, Inc.
http://www.subband.com
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
