+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
- <HEAD>
- <TITLE> [IRCServices Coding] DUMPCORE only unhandles SIGSEGV?
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20DUMPCORE%20only%20unhandles%20SIGSEGV%3F&In-Reply-To=3f0f0060.56561%40achurch.org">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="002105.html">
- <LINK REL="Next" HREF="002107.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?</H1>
- <B>Finny Merrill</B>
- <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20DUMPCORE%20only%20unhandles%20SIGSEGV%3F&In-Reply-To=3f0f0060.56561%40achurch.org"
- TITLE="[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?">griever at t2n.org
- </A><BR>
- <I>Fri Jul 11 11:25:02 PDT 2003</I>
- <P><UL>
- <LI>Previous message: <A HREF="002105.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?
-</A></li>
- <LI>Next message: <A HREF="002107.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#2106">[ date ]</a>
- <a href="thread.html#2106">[ thread ]</a>
- <a href="subject.html#2106">[ subject ]</a>
- <a href="author.html#2106">[ author ]</a>
- </LI>
- </UL>
- <HR>
-<!--beginarticle-->
-<PRE>On Sat, 12 Jul 2003 03:19:34 JST, Andrew Church <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A>>
-wrote:
-
-><i> SIGFPE only happens on divide by zero, and in the few places where
-</I>><i> Services divides by a variable the variable is already tested for being
-</I>><i> nonzero. SIGQUIT is user-generated. SIGABRT isn't generated at all.
-</I>><i> SIGILL only occurs if your compiler is broken or you run a binary
-</I>><i> compiled
-</I>><i> for the wrong CPU.
-</I>><i>
-</I>
-Well, we recently had a problem where our services (not ircservices but
-based on it)
-went into a spinlock, and there was no way we could even find out what it
-was because
-as soon as it happened the process monitor killed it for eating CPU, and
-there was no
-way we could get it to core. This has never happened to me with
-ircservices, but what
-if it did one day? The same problems would occur.
-</PRE>
-
-<!--endarticle-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="002105.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?
-</A></li>
- <LI>Next message: <A HREF="002107.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#2106">[ date ]</a>
- <a href="thread.html#2106">[ thread ]</a>
- <a href="subject.html#2106">[ subject ]</a>
- <a href="author.html#2106">[ author ]</a>
- </LI>
- </UL>
-
-</body></html>