> I'm still getting segfaults with lame 3.56... am I the only one who is
> having these problems? They began when I started using 3.50... I'm
> afraid I don't recall which previous version worked without trouble for
> me...
If you build with debugging symbols, you'll get a core file that will happily
tell a debugger like GDB where the segfault happened. This core file is quite
useful in a bug report :-)
In the case of a creeping corruption, the core will tell the final failure that
killed the program, but perhaps not the original corruption that started the
mess. By building LAME with Electric Fence, your core file will have a big red
arrow pointed at the first fault. Although I don't code for LAME, I can say
that this extra little help on the part of someone reporting a bug in one of my
own packages is a major help; they need only mail the core and the executable,
and I have all the information I need.
Monty
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
