> My Graveyard area (formerly of Kallisti fame) has been converted
> to Circle 2.2 and made public domain. You will find it at:
>
> ftp://ftp2.circlemud.org/pub/CircleMUD/incoming
>
> The file name is: grave.tar.gz
>
This has now been moved to the contrib/areas/ directory. Thanks for
the contribution.
--
Erm... Yeah. Whatever.
From icarus@berkshire.net Sat, 06 Jul 96 20:00:04 -0500
X-SystemInfo: MyE-Mail: EMail
X-Message-No: 2036 (database)
From: icarus <icarus@berkshire.net>
To: circle <circle@pvv.ntnu.no>
Subject: SEMI-OFF-TOPIC: Signal handling
Date: Sat, 6 Jul 96 20:00:00
Message-ID: <199607070008.UAA28766@loomis.berkshire.net>
X-POP3-Rcpt: lk4150@per
Return-Path: owner-circle@pvv.ntnu.no
Received: from flipper.pvv.ntnu.no (43@flipper.pvv.ntnu.no [129.241.210.200]) by per.cybercity.dk (8.6.12/8.6.12) with ESMTP id BAA02826 for <lk4150@krull.dk>; Sun, 7 Jul 1996 01:46:09 +0200
Received: (from majordomo@localhost) by flipper.pvv.ntnu.no (8.7.5/8.6.12) id CAA17155 for circle-outgoing; Sun, 7 Jul 1996 02:08:51 +0200
Received: from loomis.berkshire.net (root@berkshire.net [206.72.196.10]) by flipper.pvv.ntnu.no (8.7.5/8.6.12) with ESMTP id CAA17138 for <circle@pvv.ntnu.no>; Sun, 7 Jul 1996 02:08:21 +0200
Received: from icarus (icarus.berkshire.net [206.72.196.234]) by loomis.berkshire.net (8.7.1/8.7.1) with SMTP id UAA28766 for <circle@pvv.ntnu.no>; Sat, 6 Jul 1996 20:08:42 -0400 (EDT)
X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v0.99z
Sender: owner-circle@pvv.ntnu.no
Precedence: bulk
When signals, particularly SIGSEGV, are dispatched, is there a perceptible
delay between the generation and the receipt by the offending process? In
other words, if you wrote this program:
#include <stdio.h>
void (*function)(void); /* this looks wrong, but you get the idea. */
void main(void)
{
int i;
for(i = 1; i <= 10; i++) {
if(i == 5) {
function = NULL;
function();
}
printf("%d\t", i);
}
}
would it be possible to get this as output:
1 2 3 4 5 6 7
Segmentation fault
I ask because this seems to be happening to me. I consistently get a
segmentation fault after someone logs off (it's my fault, I added stuff
there), but also consistently in a different place every time. I got so
desperate that I now have the MUD displaying a message every line of code,
since my gdb is broken, until the moment of termination. (Well, not the
*entire* MUD; just the logoff stuff.)
It's very strange. I've tried with both a custom and the default signal
handlers and it seems to make no significant difference. Can anyone
provide any help as to why this is happening?
---------------------------------------------------------------------------
Barid Bel Medar
icarus@berkshire.net Knights of the Cosmos Shayol Ghul
Resort and Health Spa
---------------------------------------------------------------------------
"I am returning this otherwise good typing paper to you because
someone has printed gibberish all over it and put your name at
the top."
- English Professor, Ohio University
---------------------------------------------------------------------------
This archive was generated by hypermail 2b30 : 12/07/00 PST