On 8/16/05, r_zaca <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I have a program that just stops execution and I can't see what is really
> going on. Does anyone know how this kind of problem shoud be solved. I've
> already read something about core dump memory, but I don't know how to make
> it, or instruct my program to do that. Can anyone help me?
When a (UNIX) program exits abnormally it usally has received a signal
and probably has, depending on the signal (SIGSEGV, for example),
written a core dump. You can then examine the core dump by running
gdb:
$ gdb myapp core.1234
gdb usually jumps straight to the line where the crash occured.
If your program does not generate a core dump you can force it to do
so by calling abort(). A better solution is to provide an error
handler that automatically writes a core dump.
Regards
\Steve
--
Steve Graegert <[EMAIL PROTECTED]>
Software Consultancy {C/C++ && Java && .NET}
Mobile: +49 (176) 21248869
Office: +49 (9131) 7126409
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming"
in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
