Re: Segfault problem with PHP5
| From: | håvard eide | Date: | Tue, 27 Jul 2004 07:00:24 +0000 |
| Subject: | Re: Segfault problem with PHP5 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-11581@lists.php.net to get a copy of this message | ||
Trying again with a link to the file:
Just ran it through valgrind with the options that Rasmus suggested
and got a output file: http://www.ikomm.no/valgrind/out.pid27848 I
can see what'
happening, but have no idea where to go from here.
Can someone have a look at it?
Cheers
> > If the segfault was the same everytime it should be easy to track
> > down, but I've had a large amount of different segfaults running
> > apache through gdb. The other thing is that one screen can be loaded
> > different times before the segfault comes as well, sometimes the
> > segfault comes straight away, other times after 5-6 reloads of the
> > same screen.
>
> This tends to be the sort of problem where Valgrind can be very useful.
> It sounds like memory corruption somewhere.
>
> Run it like this:
>
> valgrind --leak-check=yes --show-reachable=yes --num-callers=16 --error-limit=no
> --tool=memcheck --logfile=out /usr/bin/apache -X
>
> Then hit the server and have a look at the out.<pid> file.
>
> -Rasmus
>
--
www.phpvolcano.com