I have a little program to play audio CDs (CDDA or Red Book). Once in a while the program debuts by giving 'Segmentation fault'. Today, invoking in such a way as to play a CD I had in the drive, it gave this message. Then I ran it with only option -h (give help and exit). No problem here. I ran it a third time thus

lazy -d

This makes the program, lazy, to just play the CD through, but -d instructs lazy to pick up the audio signal from the drive IDE bus instead of from the optical drive analog output (they used to have one). The result was:

I normaly invoke 'lazy -d -f /dev/hdd -o <some_track_number>, where -f admits a device name to look for the media, and have no trouble, except, as told, in the few instances where I get segmentation fault.
But this time I have that new diagnostic element: the malloc message. Can this help to determine the cause of the segmentation fault. I have the sources of lazy.

EDIT: at the time of these runs of the program, X was running too and five instances of the web browser. Plus the memory installed in my machine is only 256MB (but this satisfies Volkerdi's requirements).OK. Then I exited X and rerun lazy, only to get the malloc message again. Does not X return the memory to the system pool when exiting?

Kernel 2.6.21.5, slackware 12.0

When a process exits the OS should reclaim it resources it has used. For this reason I don't think the problem is X espically if you have killed of X. I would run top to see an overview of system processes and that you can get a idea of which if any processes or causing the issue. Having said that 256M is a little on the small side. In order to get it run properly you may need to get more ram or do some slimming on what processes are booted up at run time