I've set up a web server on a RootBSD VPS with Lighttpd and PHP via FastCGI to operate a site with the Drupal CMS. When I take a certain, repeatable series of steps in Drupal, I'm causing the PHP process to exit on signal 11, a segmentation fault.

I've already spent several hours over the past couple of weeks diagnosing this through trial and error, but haven't been able to figure out what's causing this or how to work around it. Even more flummoxing is that my company also has a RootBSD VPS account which is not having this problem. Their account is a step above mine and has a larger memory allocation, so I suspect that might be the problem or at least part of it, but I'm not sure.

I guess what I'm asking is, is there a way to get more information on what is causing such an error, or perhaps even where in Drupal's codebase it's occurring?

It does, though since it tends to put it in a random Drupal directory, I have to use the find command to find it. However, once I studied up a bit on gdb, I couldn't get it to tell me anything useful:

Code:

> gdb -c /usr/local/www/www/sites/all/modules/nice_menus/php-cgi.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Core was generated by `php-cgi'.
Program terminated with signal 11, Segmentation fault.
#0 0x288f9107 in ?? ()
(gdb) bt
#0 0x288f9107 in ?? ()
Cannot access memory at address 0xbf9ffcb0
(gdb) exit

And after I compiled PHP with the Debug flag, it wasn't able to find the PHP extensions, causing other unrelated errors. =[

Quote:

Also, what exactly are you doing in drupal to cause this error?

I am enabling CSS optimization. This feature basically concatenates the various CSS files the site uses so that all the CSS is together in one file. Drupal sites can easily end up with a number of CSS files in the low teens at the least, so this feature is pretty important for production sites.