From: Francis Lau <fkwlau@utcc.utoronto.ca>
To: Matthew Studley <matthew.studley@uwe.ac.uk>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: what causes SIGTERMs?
Date: Tue, 8 Jul 2003 09:26:46 -0400 [thread overview]
Message-ID: <Pine.LNX.4.44.0307080924030.17500-100000@gpu.utcc> (raw)
In-Reply-To: <00be01c34553$57ea97a0$caba0ba4@uwe.ac.uk>
A link that gives a simple explanation on what SIGTERM and SIGKILL mean:
http://www.gnu.org/manual/glibc-2.2.5/html_node/Termination-Signals.html
>
> I wonder whether you could help me? I have a problem; I'm running an
> application I've written in C under Slackware 7.1 Occasionally it receives
> a SIGTERM.
>
> * In what circumstances do processes get sent a SIGTERM?
>
> * Am I correct that this is unlikely to be issued in response to a bug in my
> code?
>
> * How can I find which process is issuing the SIGTERM against my code?
Perhaps use strace or gdb to see where the code is dying?
>
> * Are there any changes I can make to the execution environment / logging /
> gcc compilation options to help me find out why this is happening?
compiel with -g for more debugging information
Hope it helps,
Francis
next prev parent reply other threads:[~2003-07-08 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 13:17 what causes SIGTERMs? Matthew Studley
2003-07-08 13:26 ` Francis Lau [this message]
2003-07-08 14:27 ` Glynn Clements
2003-07-09 15:36 ` Matthew Studley
2003-07-10 2:12 ` Glynn Clements
2003-07-10 9:50 ` linking at run time John T. Williams
2003-07-10 7:18 ` nanakos
2003-07-10 8:34 ` Mohan Rao A. J.
2003-07-11 9:51 ` Progga
2003-07-22 14:54 ` what causes SIGTERMs? Matthew Studley
2003-07-22 15:11 ` Jan-Benedict Glaw
2003-07-22 20:47 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 19:16 Jad Saklawi
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=Pine.LNX.4.44.0307080924030.17500-100000@gpu.utcc \
--to=fkwlau@utcc.utoronto.ca \
--cc=linux-c-programming@vger.kernel.org \
--cc=matthew.studley@uwe.ac.uk \
/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).