www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Kuhn <wk...@sun1.uconect.net>
Subject os-linux/165: #exec cmd results in SIGSEGV (dumping core)
Date Thu, 06 Feb 1997 20:20:01 GMT

	The contract type is `' with a response time of 3 business hours.
	A first analysis should be sent before: Thu Feb 06 15:00:01 PST 1997


>Number:         165
>Category:       os-linux
>Synopsis:       #exec cmd results in SIGSEGV (dumping core)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb  6 12:20:01 1997
>Originator:     wkuhn@uconect.net
>Organization:
apache
>Release:        1.1.1
>Environment:
Redhat 2.0.18
compiled with gcc version 2.7.2
>Description:
I upgraded from redhat 1.2.13 to 2.0.18.  Upon upgrading I have been receiving
 httpd: caught SIGSEGV, dumping core in my error log when I hit a page with a
#exec cmd directive.  #exec cgi directives work fine, but I need to pass
arguments so it doesn't solve my problem at hand.  My #exec cmd programs are
written in perl 5.003, but I tried a simple ksh script also and apache dumped
core.

I tend to believe that this is a linux version bug, but I figured I would submit
a bug report here just in case anyone encounters a similar problem (and finds a
solution?).
>How-To-Repeat:
Aside from logging into my machine and poking around I am not sure how you can
repeat the problem.
>Fix:
no
>Audit-Trail:
>Unformatted:



Mime
View raw message