On 2/26/07, Vladimir Konrad <v.konrad / lse.ac.uk> wrote:
>
> i have a long running script which takes a lot netcdf files and
> generates SQL which get's piped to another process for database import.
> the script failed about 1/2 way through (after about 5 days) with
> segmentation fault.
>
> is there a way to debug segfaulting script (i.e. is there a way to
> generate core file) so i can find out more?
>
> my understanding is that segmentation fault is usually caused by
> addressing memory which does not belong to the process (bad pointer and
> such).
>
> --- using
> ruby 1.8.2 (2005-04-11) [i386-linux]
> ---
> vlad

I suppose that linux makes core dumps unless it is told not to do
(using ulimit). You can inspect the core file with gdb. It may be
helpful to have symbols table available (i.e. not stripped ruby).

Now, don't take this as too accurate... Last time I debugged a core
file was in 1999...