projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] DUMPCORE only unhandles SIGSEGV? | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <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"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="002105.html"> | |
| 11 | <LINK REL="Next" HREF="002107.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?</H1> | |
| 15 | <B>Finny Merrill</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20DUMPCORE%20only%20unhandles%20SIGSEGV%3F&In-Reply-To=3f0f0060.56561%40achurch.org" | |
| 17 | TITLE="[IRCServices Coding] DUMPCORE only unhandles SIGSEGV?">griever at t2n.org | |
| 18 | </A><BR> | |
| 19 | <I>Fri Jul 11 11:25:02 PDT 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="002105.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV? | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="002107.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV? | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#2106">[ date ]</a> | |
| 27 | <a href="thread.html#2106">[ thread ]</a> | |
| 28 | <a href="subject.html#2106">[ subject ]</a> | |
| 29 | <a href="author.html#2106">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <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>> | |
| 35 | wrote: | |
| 36 | ||
| 37 | ><i> SIGFPE only happens on divide by zero, and in the few places where | |
| 38 | </I>><i> Services divides by a variable the variable is already tested for being | |
| 39 | </I>><i> nonzero. SIGQUIT is user-generated. SIGABRT isn't generated at all. | |
| 40 | </I>><i> SIGILL only occurs if your compiler is broken or you run a binary | |
| 41 | </I>><i> compiled | |
| 42 | </I>><i> for the wrong CPU. | |
| 43 | </I>><i> | |
| 44 | </I> | |
| 45 | Well, we recently had a problem where our services (not ircservices but | |
| 46 | based on it) | |
| 47 | went into a spinlock, and there was no way we could even find out what it | |
| 48 | was because | |
| 49 | as soon as it happened the process monitor killed it for eating CPU, and | |
| 50 | there was no | |
| 51 | way we could get it to core. This has never happened to me with | |
| 52 | ircservices, but what | |
| 53 | if it did one day? The same problems would occur. | |
| 54 | </PRE> | |
| 55 | ||
| 56 | <!--endarticle--> | |
| 57 | <HR> | |
| 58 | <P><UL> | |
| 59 | <!--threads--> | |
| 60 | <LI>Previous message: <A HREF="002105.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV? | |
| 61 | </A></li> | |
| 62 | <LI>Next message: <A HREF="002107.html">[IRCServices Coding] DUMPCORE only unhandles SIGSEGV? | |
| 63 | </A></li> | |
| 64 | <LI> <B>Messages sorted by:</B> | |
| 65 | <a href="date.html#2106">[ date ]</a> | |
| 66 | <a href="thread.html#2106">[ thread ]</a> | |
| 67 | <a href="subject.html#2106">[ subject ]</a> | |
| 68 | <a href="author.html#2106">[ author ]</a> | |
| 69 | </LI> | |
| 70 | </UL> | |
| 71 | ||
| 72 | </body></html> |