[xdebug-general] Re: Seg faults galore

From: Jeremy Knope <jerome[@]rainstormconsulting.com>
Date: Mon, 9 Oct 2006 16:43:53 -0400

Thanks, I'll try this tomorrow, it worked once today but turned out
to be a PDO bug in that particular instance, possible that some of
the others were this PDO bug also. Of course things are wonderous in
PHP 5.2RC since PDO is fixed in that but xdebug doesn't seem to work
in that so hard to say. My attempts of running gdb after the first
were met with an unresponsive web server on every attempt, so maybe
tomorrow I'll have better luck.
  -- jerome

Jeremy Knope
Web Developer
Rainstorm Consulting: http://www.rainstormconsulting.com
"Designing Strategies for Internet Success."
Phone: 207-866-3908
Fax: 207-866-0297

On Oct 9, 2006, at 1:07 PM, Derick Rethans wrote:

> On Mon, 9 Oct 2006, Jeremy Knope wrote:
>> I'm having a hard time, at least with Xdebug 2.0.0 RC1, I still
>> have to see if
>> reverting to beta6 makes any difference, but I'm getting PHP/
>> Apache childs seg
>> faulting like crazy from within my application environment.
>> Sometimes when
>> doing var_dump then exit(), but I'm having a hard time tracing any
>> particular
>> action that causes it. Anybody have a clue how to narrow it down
>> to what's
>> possibly happening? way to get a dump of the crashed apache process?
> This sounds fishy. I've been running Xdebug with valgrind with quite a
> bit of apps without any notices or warnings. What you can try is the
> following:
> # apachectl stop
> # gdb /path/to/apachesrc-tree/src/httpd
> (gdb) run -X
> and then start requesting your scripts until it crashes. GDB should
> then
> allow you to enter commands. Enter "bt" to get a backtrace. Once you
> have that, please post it here.
> regards,
> Derick
> --
> Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org
Received on Mon Oct 09 2006 - 22:44:11 BST

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST