From owner-freebsd-ports@FreeBSD.ORG Sun Sep 14 15:46:19 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDCF106564A for ; Sun, 14 Sep 2008 15:46:19 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 13A228FC1A for ; Sun, 14 Sep 2008 15:46:18 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ketnh-0004U5-S5 for freebsd-ports@freebsd.org; Sun, 14 Sep 2008 15:46:13 +0000 Received: from 85.48.193.152 ([85.48.193.152]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Sep 2008 15:46:13 +0000 Received: from matiassurdi by 85.48.193.152 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Sep 2008 15:46:13 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Matias Surdi Date: Sun, 14 Sep 2008 17:45:59 +0200 Lines: 47 Message-ID: References: <20080912095828.GA52822@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 85.48.193.152 User-Agent: Thunderbird 2.0.0.16 (X11/20080724) In-Reply-To: <20080912095828.GA52822@icarus.home.lan> Sender: news Subject: Re: mod_python core dump X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2008 15:46:19 -0000 Jeremy Chadwick escribió: > On Fri, Sep 12, 2008 at 11:39:35AM +0200, Matias Surdi wrote: >> I've installed mod_python from the ports on a recently installed FreeBSD >> 7 box and, despite all the build process goes well, when I try to start >> apache I get a core dump. If I disable the "Loadmodule" directive for >> mod_python in httpd.conf, then apache starts perfectly. >> >> The versions I'm using are: >> >> # pkg_version -v >> apache-2.0.63_2 = up-to-date with port >> autoconf-2.62 = up-to-date with port >> autoconf-wrapper-20071109 = up-to-date with port >> bash-3.2.39_1 = up-to-date with port >> dovecot-1.1.3 = up-to-date with port >> expat-2.0.1 = up-to-date with port >> gettext-0.17_1 = up-to-date with port >> gmake-3.81_3 = up-to-date with port >> help2man-1.36.4_2 = up-to-date with port >> libiconv-1.11_1 = up-to-date with port >> libtool-1.5.26 = up-to-date with port >> linux_base-fc-4_10 < needs updating (port has 4_13) >> m4-1.4.11,1 = up-to-date with port >> mod_python-3.3.1_2 = up-to-date with port >> p5-gettext-1.05_2 = up-to-date with port >> pcre-7.7_1 = up-to-date with port >> perl-5.8.8_1 = up-to-date with port >> pkg-config-0.23_1 = up-to-date with port >> postfix-2.5.4,1 = up-to-date with port >> py25-sqlite3-2.5.2_1 = up-to-date with port >> python25-2.5.2_3 = up-to-date with port >> sqlite3-3.5.6 = up-to-date with port >> >> Any help will be appreciated, thanks. > > You'll need to provide a gdb backtrace to determine the cause of the > core, and provide any error messages shown in Apache's error log > (default: /var/log/httpd-error.log). The above information doesn't > provide enough detail. > > Please also be aware that, quite often, debugging Apache and Apache > modules is a tedious and difficult task. It's rarely a simple thing. > I've noticed that compiling python without threads support fixes the problem, but that's not a solution for me as I need threads. Any other ideas?