All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Graegert <graegerts@gmail.com>
To: r_zaca <r_zaca@ig.com.br>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Program execution
Date: Tue, 16 Aug 2005 17:16:09 +0200	[thread overview]
Message-ID: <6a00c8d5050816081662861713@mail.gmail.com> (raw)
In-Reply-To: <20050816_143050_024141.r_zaca@ig.com.br>

On 8/16/05, r_zaca <r_zaca@ig.com.br> 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 <graegerts@gmail.com>
Software Consultancy {C/C++ && Java && .NET}
Mobile: +49 (176)  21248869
Office: +49 (9131) 7126409

      parent reply	other threads:[~2005-08-16 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 14:30 Program execution r_zaca
2005-08-16 14:48 ` Markus Rechberger
2005-08-16 15:16 ` Steve Graegert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a00c8d5050816081662861713@mail.gmail.com \
    --to=graegerts@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=r_zaca@ig.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.