Also here, best to have a short 10-20 line reproducing script.
Andi
At 12:19 PM 10/14/2002 +0200, Jan Schneider wrote:
>Zitat von Yasuo Ohgaki <[EMAIL PROTECTED]>:
>
> > > 0x4055778f in _efree (ptr=0x83476e4)
> > > at /home/jan/software/php4/Zend/zend_alloc.c:229
> > > 229 REMOVE
Can you give the source for that function and the arguments it's being
passed/context it is used in?
Jan Schneider wrote:
>Zitat von Yasuo Ohgaki <[EMAIL PROTECTED]>:
>
>>>0x4055778f in _efree (ptr=0x83476e4)
>>>at /home/jan/software/php4/Zend/zend_alloc.c:229
>>>229 REMOVE_POIN
Zitat von Yasuo Ohgaki <[EMAIL PROTECTED]>:
> > 0x4055778f in _efree (ptr=0x83476e4)
> > at /home/jan/software/php4/Zend/zend_alloc.c:229
> > 229 REMOVE_POINTER_FROM_LIST(p);
> > (gdb) bt
> > #0 0x4055778f in _efree (ptr=0x83476e4)
> > at /home/jan/software/php4/Zend/zend_all
Jan Schneider wrote:
> Hi,
>
> the segfaults still occur, though on a different machine (pretty vanilla
> suse 8.0). But now I get a more useful bt:
>
> 0x4055778f in _efree (ptr=0x83476e4)
> at /home/jan/software/php4/Zend/zend_alloc.c:229
> 229 REMOVE_POINTER_FROM_LIST(p);
> (gd
Hi,
the segfaults still occur, though on a different machine (pretty vanilla
suse 8.0). But now I get a more useful bt:
0x4055778f in _efree (ptr=0x83476e4)
at /home/jan/software/php4/Zend/zend_alloc.c:229
229 REMOVE_POINTER_FROM_LIST(p);
(gdb) bt
#0 0x4055778f in _efree (ptr=0x
Zeev Suraski wrote:
> Try reducing IMP to the smallest possible script that still reproduces
> the problem (crashes). That will give us something to go on. Chances
> are it's not a crash in the engine.
Optionally, see "Locating which function call caused segfault" section
http://bugs.php.net/
Derick Rethans wrote:
>On Mon, 7 Oct 2002, Jan Schneider wrote:
>
>
>
>>In another script the segfaults occur in another place. It's hard to
>>trap it down cause it happens during inside a foreach loop. It doesn't
>>happen after the first loop but at any of the subsequent loops. Inside
>>thi
On Mon, 7 Oct 2002, Jan Schneider wrote:
> In another script the segfaults occur in another place. It's hard to
> trap it down cause it happens during inside a foreach loop. It doesn't
> happen after the first loop but at any of the subsequent loops. Inside
> this loop happens - beside a call
Jan Schneider wrote:
> Zeev Suraski wrote:
>
>> Try reducing IMP to the smallest possible script that still
>> reproduces the problem (crashes). That will give us something to go
>> on. Chances are it's not a crash in the engine.
>
>
> This one's really strange and I'm afraid not very helpful.
ot; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, October 07, 2002 6:28 PM
Subject: Re: [PHP-DEV] Segfaults in Zend
> Zeev Suraski wrote:
>
> > Try reducing IMP to the smallest possible script that still reproduces
> > the problem (crashes). That will give us som
Zeev Suraski wrote:
> Try reducing IMP to the smallest possible script that still reproduces
> the problem (crashes). That will give us something to go on. Chances
> are it's not a crash in the engine.
This one's really strange and I'm afraid not very helpful.
PHP segfaults while returning f
hmmm yeah, that is the question !
- Original Message -
From: "Zeev Suraski" <[EMAIL PROTECTED]>
To: "Jan Schneider" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, October 07, 2002 5:29 PM
Subject: Re: [PHP-DEV] Segfaults in Zend
>
Try reducing IMP to the smallest possible script that still reproduces the
problem (crashes). That will give us something to go on. Chances are it's
not a crash in the engine.
At 18:37 07/10/2002, Jan Schneider wrote:
>Zeev Suraski wrote:
>
>>What are you doing in order to get it to crash?
>
>
Zeev Suraski wrote:
> What are you doing in order to get it to crash?
Calling any page in IMP. This is why I don't know exactly _where_ it
segfaults.
I don't have an apache version with debug information at hand, so I
can't give you more bt details, sorry.
--
PHP Development Mailing List
What are you doing in order to get it to crash?
At 18:20 07/10/2002, Jan Schneider wrote:
>Hi,
>
>I currently get following segfaults:
>
>httpd logs:
>
>[Mon Oct 7 17:17:45 2002] [notice] child pid 19460 exit signal
>Segmentation fault (11)
>FATAL: emalloc(): Unable to allocate 1515870812 byt
Hi,
I currently get following segfaults:
httpd logs:
[Mon Oct 7 17:17:45 2002] [notice] child pid 19460 exit signal
Segmentation fault (11)
FATAL: emalloc(): Unable to allocate 1515870812 bytes
I can understand him well ;-)
BT:
Program received signal SIGSEGV, Segmentation fault.
0x400d1
16 matches
Mail list logo
