Michael C. Neel
neel at mediapulse.com
Fri Sep 13 11:12:55 EST 2002
I take it you are having a similar problem? I'm not able to get gdb to run on apache2; it runs but I cannot connect to it. I'm not really familiar with gdb, so I'm not sure what I have to do to get it to run. I'm trying out compiling mod_python with different arguments to see if anything fixes it. It might also be python 2.2, I need to upgrade to 2.2.1 and see where that leads. Mike -- Michael C. Neel There are only 10 types of people in the world; those who understand binary and those who don't. -----Original Message----- From: Martin Pool [mailto:mbp at samba.org] Sent: Friday, September 13, 2002 5:47 AM To: Jeff Davis Cc: Michael C. Neel; mod_python at modpython.org Subject: Re: [mod_python] Mod_Python 3 / Apache 2 / RedHat 7.3 / Python 2.2 = Seg fault :( On 13 Sep 2002, Jeff Davis <list-mod_python at empires.org> wrote: > > Try running apache under gdb? Something like this: > > > > # gdb /usr/sbin/apache2 > > [blah blah] > > gdb> run -X > > > > Then try to access a page. Apache should stop in gdb, and it might > > tell you where the problem is. > > I tried both gdb and valgrind and supplied the -X argument for each. When I > hit a page, all it said was "Segmentation Fault" (for valgrind, and gdb was > similar: "Program received signal SIGSEGV, Segmentation fault."). GDB also > said "0x402611bb in strlen () from /lib/libc.so.6" after the SIGSEGV, which > might be helpful. OK, good. Now once you get to that point, type gdb> backtrace full to get some info on where the call to strlen() that caused trouble came from. -- Martin
|