This is IIRC... somebody correct me if I'm wrong:
For future reference (because it's easier), you can use gdb directly to get
your backtrace without having to modify your config
file. You just launch httpd through gdb like so, then tell gdb
to set the -X argument and run the program:
# gdb /path/to/httpd
(gdb) set args -X
(gdb) run
Then do whatever it is that makes Apache segfault. gdb will stop the
program upon the segv and leave the core in memory so you can do your
backtrace or whatever.
--Cliff
Cliff Woolley
Central Systems Software Administrator Washington and Lee University http://www.wlu.edu/~jwoolley/ Work: (540) 463-8089
Pager: (540) 462-2303 >>> [EMAIL PROTECTED] 05/09/00 04:14AM >>>
OK guys, thanks very much for your help. I've managed to get a backtrace by following Gianni's suggestion and running httpd under gdb. |
- Segmentation fault but even httpd -X == no core dump??? Philip Payne
- Re: Segmentation fault but even httpd -X == no core du... Gianni Mariani
- RE: Segmentation fault but even httpd -X == no cor... Kirk Benson
- Re: Segmentation fault but even httpd -X == no... Philip Payne
- Re: Segmentation fault but even httpd -X == no cor... Philip Payne
- Re: Segmentation fault but even httpd -X == no core du... Winged Wolf
- Re: Segmentation fault but even httpd -X == no core du... kbarrass
- Re: Segmentation fault but even httpd -X == no core du... Philip Payne
- Cliff Woolley