Perhaps you could run Apache as a single foreground process under GDB:
gdb /usr/sbin/httpd
(gdb) run -X
Then at least you'll know what library the segfault is occurring in.
On Tue, Mar 14, 2006 at 06:12:51PM +1100, Alec Thomas wrote:
> To add some more data to this, I'm running trunk on TracHacks with a
> similar setup (though different versions of all the components) and
> haven't experienced any crashes:
>
> configuration: Linux 2.6.12-i686 P4 2.8GHZ
> clearsilver 0.10.1-1
> pysqlite 2.0.5-1
> sqlite3 3.3.4-1
> apache2 2.0.55-1
> mod_python 3.1.4-1
> python 2.4.2-1
>
> So it looks like somewhere between your versions and my versions
> something got fixed! Useful eh? :)
>
> On Mon, Mar 13, 2006 at 11:33:08PM +0100, Emmanuel Blot wrote:
> > Hi,
> >
> > I experience a fully reproducible crash of Trac since I upgraded Trac
> > with WSGI support.
> >
> > When I write "crash", I do not mean a Trac python exception: the
> > actual error is worse: the Apache thread that handle the request
> > crashes !
> >
> > The exact log message from Apache is:
> >
> > " child pid 16662 exit signal Segmentation fault (11) "
> >
> > To ease debugging:
> >
> > 1/ I've disabled any Trac extension (I get rid of the 'egg' directory,
> > so I'm sure no egg is loaded)
> > 2/ I run Trac from the original sources (i.e. svn co
> > http://pec/svn/trac/trunk/trac /var/trac, and mod_python is given
> > /var/trac as the pythonpath, i.e. I do not use the installer)
> >
> > Important: the trouble (crash) occurs ONLY when the user is
> > authenticated. In other word, I can access the WikiStart page with no
> > issue. As soon as I log in on the server, it crashes (I never bet the
> > 'logged in as ...' page).
> >
> > trunk:2954 works with no issue
> > trunk:2963 crashes
> >
> > intermediate releases [2957...2962] are not really usable (typos,
> > mod_python issue)
> >
> > The issue does not occur on a Windows (XP SP2) machine, with a similar
> > configuration.
> >
> > On the Linux machine, 2954 works with the very same configuration that
> > makes 2963 crash (same sqlite, pysqlite, clearsilver, etc.)
> >
> > Is this a known issue ? Where should I look at to find other piece of info ?
> >
> > configuration: Linux 2.6.12-1-i686 (Debian/testing, AMD Athlon 1GHz)
> > clearsilver: 0.9.13-3.2
> > python2.3-sqlite: 1.0.1-4
> > libsqlite0: 2.8.16-1
> > apache2-mpm-prefork: 2.0.55-4
> > libapache2-mod-python2.3: 3.1.3-3
> > python2.3: 2.3.5-9.1
> >
> > --
> > Manu
> > _______________________________________________
> > Trac mailing list
> > [email protected]
> > http://lists.edgewall.com/mailman/listinfo/trac
> >
>
> --
> Evolution: Taking care of those too stupid to take care of themselves.
> _______________________________________________
> Trac mailing list
> [email protected]
> http://lists.edgewall.com/mailman/listinfo/trac
>
--
Evolution: Taking care of those too stupid to take care of themselves.
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
