We're also frustrated with PHP segfaults running our symfony project - and we're also working around by calling ->__toString() explicitly
We got as far as building PHP with --enable-debug and getting a backtrace from gdb, http://bugs.php.net/bug.php?id=47522 - but we were unable to create a short example script - it seems whenever we removed something from our larger symfony project, to isolate the segfault, the segfault would disappear Casting the object to a string in a parent function does not produce a segfault, while calling a function and casting in the called function does. Even passing the object as the first as opposed to fourth argument of the function causes the segfault to disappear. We're not using XCache or Memcache On Jun 24, 3:37 am, skr <[email protected]> wrote: > On 23 Jun., 18:22, Bernhard Schussek <[email protected]> wrote:> Hi, > > > Do you have XDebug installed? I found that XDebug sometimes gives > > useful error messages when plain PHP segfaults. > > Just installed it - but it shows nothing, just 3 segfaults per > request... > > [Wed Jun 24 09:32:36 2009] [notice] child pid 9081 exit signal > Segmentation fault (11) > [Wed Jun 24 09:32:37 2009] [notice] child pid 9082 exit signal > Segmentation fault (11) > [Wed Jun 24 09:32:37 2009] [notice] child pid 9083 exit signal > Segmentation fault (11) > > So I used the old way of inserting a lot of echo's and found out, that > inserting a ->__toString() cured this segfault. > (I gave an object to a function wanting a string) > > Completely unrelated to symfony.... > > But xdebug is helpful, thanks for the hint. > > Konrad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
