From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: what causes SIGTERMs?
Date: Tue, 22 Jul 2003 17:11:21 +0200 [thread overview]
Message-ID: <20030722151118.GT7452@lug-owl.de> (raw)
In-Reply-To: <008101c35061$18aebb20$caba0ba4@uwe.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Tue, 2003-07-22 15:54:04 +0100, Matthew Studley <matthew.studley@uwe.ac.uk>
wrote in message <008101c35061$18aebb20$caba0ba4@uwe.ac.uk>:
> A brief follow-up
>
> > > > * Am I correct that this is unlikely to be issued in response to a bug
> > in my
> > > > code?
>
> As it turns out, this was issued in response to a runaway memory leak in my
> code. Still not sure where the signal came from.
So, most probably you got SIGTERMinated by the kernel at some
out-of-memory situation after you grew too large...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-22 15:11 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
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 [this message]
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=20030722151118.GT7452@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).