From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Forcing a core dump
Date: Sat, 21 Aug 2004 22:08:28 +0200 [thread overview]
Message-ID: <20040821200828.GW16935@lug-owl.de> (raw)
In-Reply-To: <412622F5.2080208@fi.uba.ar>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Fri, 2004-08-20 13:12:37 -0300, Darío Mariani <dmarian@fi.uba.ar>
wrote in message <412622F5.2080208@fi.uba.ar>:
> Hello:
> Is it possible to force a running program to generate a core dump. My
> problem is that I have a program that, from time to time, it freezes and
> I want to know what's going on.
SIGABRT is ment to do exactly that. However, "ulimit" must allow for the
core to be created and core dumps won't work with multi-threaded
programs (I heared rumors that this was changed in 2.6.x).
Also, in cases of a freeze, attaching a debugger (gdb) might help as
much:
$ gdb /path/to/your/program `pidof program`
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-21 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 10:09 Adding sysctl varaible into kernel authn
2004-08-20 16:12 ` Forcing a core dump Darío Mariani
2004-08-20 16:45 ` Eric Bambach
2004-08-20 17:33 ` Steven Smith
2004-08-21 20:08 ` Jan-Benedict Glaw [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=20040821200828.GW16935@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).