Return-Path: Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 72996 invoked by uid 500); 28 Apr 2003 11:22:15 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 72980 invoked from network); 28 Apr 2003 11:22:15 -0000 Date: Mon, 28 Apr 2003 07:22:10 -0400 (EDT) From: Norman Tuttle To: test-dev@httpd.apache.org Subject: Assert used in Flood and its triggering under Sun Solaris In-Reply-To: <3EA3EB67.5050100@siptech.co.in> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Flood Developers on Solaris / in general: The flood website says that the majority of the developers for the Flood project have developed it using Solaris and Linux. Therefore I am curious to know why I might be seeing different behavior when running keepalive socket code on Solaris (than Win32 or Linux); specifically, it fails assert code found in the source file flood_socket_keepalive.c, thus aborting in the middle of a run with a core dump. This type of behavior does not occur with the code I have running on a Win32 system. Specifically, I want to know: (1) What is the purpose of the assert here, and why might it be failing specifically on a Solaris system?, and (2) What would be a more graceful way of reporting this error rather than aborting the system with a core dump? I have an exception reporting mechanism in place, and just want to understand how the system should recover in this case. It seems that the code is highly coupled with notions of chunked encoding.