Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 59116 invoked from network); 16 Jul 2004 13:45:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Jul 2004 13:45:43 -0000 Received: (qmail 70815 invoked by uid 500); 16 Jul 2004 13:45:23 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 70733 invoked by uid 500); 16 Jul 2004 13:45:22 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 70646 invoked by uid 99); 16 Jul 2004 13:45:21 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_BY_IP,SB_NEW_BULK,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [216.239.56.250] (HELO mproxy.gmail.com) (216.239.56.250) by apache.org (qpsmtpd/0.27.1) with SMTP; Fri, 16 Jul 2004 06:45:20 -0700 Received: by mproxy.gmail.com with SMTP id q44so2490792cwc for ; Fri, 16 Jul 2004 06:45:19 -0700 (PDT) Received: by 10.11.99.40 with SMTP id w40mr254728cwb; Fri, 16 Jul 2004 06:45:19 -0700 (PDT) Message-ID: Date: Fri, 16 Jul 2004 09:45:18 -0400 From: Joshua Slive To: users@httpd.apache.org In-Reply-To: <200407160815390773.089E174E@filarescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200407160815390773.089E174E@filarescue.org> X-Virus-Checked: Checked Subject: Re: [users@httpd] uh oh... X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, 16 Jul 2004 08:15:39 -0500, Webmaster wrote: > As for the core dump, I used (for the first time) gdb to look at the core dump. When I first started gdb, it gave me: > > Core was generated by `httpd'. > Program terminated with signal 4, Illegal instruction. > #0 0x28f5f712 in ?? () There is some info here on how to debug: http://httpd.apache.org/dev/debugging.html In particular, gdb /path/to/httpd -c /path/to/core Then type "where" to get a full backtrace. This should at least let you know what module is causing the problem. The other option is to start dropping modules from your build until the problem goes away. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org