Re: [PHP-DEV] Segfaults in Zend

[Andi Gutmans]

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_POINTER_FROM_LIST(p);
> > > (gdb) bt
> > > #0  0x4055778f in _efree (ptr=0x83476e4)
> > > at /home/jan/software/php4/Zend/zend_alloc.c:229
> > > #1  0x405664a1 in _zval_dtor (zvalue=0x83456bc)
> > > at /home/jan/software/php4/Zend/zend_variables.c:44
> > > #2  0x4055e4c1 in _zval_ptr_dtor (zval_ptr=0x40605714)
> > > at /home/jan/software/php4/Zend/zend_execute_API.c:293
> > > #3  0x4057516d in execute (op_array=0x835c0c4)
> >
> > If you could tell us what execute() is trying to execute,
> > it would be useful.
>
>(gdb) frame 3
>#3  0x4057516d in execute (op_array=0x8353ebc)
> at /home/jan/software/php4/Zend/zend_execute_locks.h:26
>26  zval_ptr_dtor(&EG(garbage)[--EG(garbage_ptr)]);
>(gdb) print (char
>*)(executor_globals.function_state_ptr->function)->common.function_name
>$1 = 0x82f313c "flist"
>
>flist() is the function mentioned earlier, that segfaults while returning to
>the calling function.
>
> > Did you read my email? (and the URL?)
> > http://bugs.php.net/bugs-generating-backtrace.php
>
>Sorry, I didn't know that it has been updated with instructions on how to
>locate the segfaulting function.
>
>Jan.
>
>--
>http://www.horde.org - The Horde Project
>http://www.ammma.de - discover your knowledge
>http://www.tip4all.de - Deine private Tippgemeinschaft
>
>--
>PHP Development Mailing List 
>To unsubscribe, visit: http://www.php.net/unsub.php


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[George Schlossnagle]

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_POINTER_FROM_LIST(p);
>>>(gdb) bt
>>>#0  0x4055778f in _efree (ptr=0x83476e4)
>>>at /home/jan/software/php4/Zend/zend_alloc.c:229
>>>#1  0x405664a1 in _zval_dtor (zvalue=0x83456bc)
>>>at /home/jan/software/php4/Zend/zend_variables.c:44
>>>#2  0x4055e4c1 in _zval_ptr_dtor (zval_ptr=0x40605714)
>>>at /home/jan/software/php4/Zend/zend_execute_API.c:293
>>>#3  0x4057516d in execute (op_array=0x835c0c4)
>>>
>>If you could tell us what execute() is trying to execute,
>>it would be useful.
>>
>
>(gdb) frame 3
>#3  0x4057516d in execute (op_array=0x8353ebc)
>at /home/jan/software/php4/Zend/zend_execute_locks.h:26
>26  zval_ptr_dtor(&EG(garbage)[--EG(garbage_ptr)]);
>(gdb) print (char
>*)(executor_globals.function_state_ptr->function)->common.function_name
>$1 = 0x82f313c "flist"
>
>flist() is the function mentioned earlier, that segfaults while returning to
>the calling function.
> 
>
>>Did you read my email? (and the URL?)
>>http://bugs.php.net/bugs-generating-backtrace.php
>>
>
>Sorry, I didn't know that it has been updated with instructions on how to
>locate the segfaulting function.
>
>Jan.
>
>--
>http://www.horde.org - The Horde Project
>http://www.ammma.de - discover your knowledge
>http://www.tip4all.de - Deine private Tippgemeinschaft
>




-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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_alloc.c:229
> > #1  0x405664a1 in _zval_dtor (zvalue=0x83456bc)
> > at /home/jan/software/php4/Zend/zend_variables.c:44
> > #2  0x4055e4c1 in _zval_ptr_dtor (zval_ptr=0x40605714)
> > at /home/jan/software/php4/Zend/zend_execute_API.c:293
> > #3  0x4057516d in execute (op_array=0x835c0c4)
> 
> If you could tell us what execute() is trying to execute,
> it would be useful.

(gdb) frame 3
#3  0x4057516d in execute (op_array=0x8353ebc)
at /home/jan/software/php4/Zend/zend_execute_locks.h:26
26  zval_ptr_dtor(&EG(garbage)[--EG(garbage_ptr)]);
(gdb) print (char
*)(executor_globals.function_state_ptr->function)->common.function_name
$1 = 0x82f313c "flist"

flist() is the function mentioned earlier, that segfaults while returning to
the calling function.
 
> Did you read my email? (and the URL?)
> http://bugs.php.net/bugs-generating-backtrace.php

Sorry, I didn't know that it has been updated with instructions on how to
locate the segfaulting function.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft

-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Yasuo Ohgaki]

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);
> (gdb) bt
> #0  0x4055778f in _efree (ptr=0x83476e4)
> at /home/jan/software/php4/Zend/zend_alloc.c:229
> #1  0x405664a1 in _zval_dtor (zvalue=0x83456bc)
> at /home/jan/software/php4/Zend/zend_variables.c:44
> #2  0x4055e4c1 in _zval_ptr_dtor (zval_ptr=0x40605714)
> at /home/jan/software/php4/Zend/zend_execute_API.c:293
> #3  0x4057516d in execute (op_array=0x835c0c4)

If you could tell us what execute() is trying to execute,
it would be useful.

Did you read my email? (and the URL?)
http://bugs.php.net/bugs-generating-backtrace.php

FROM the URL.
*  Sample gdb session
(gdb) bt
#0  0x080ca21b in _efree (ptr=0xbfffdb9b) at zend_alloc.c:240
#1  0x080d691a in _zval_dtor (zvalue=0x8186b94) at zend_variables.c:44
#2  0x080cfab3 in _zval_ptr_dtor (zval_ptr=0xbfffdbfc) at zend_execute_API.c:274
#3  0x080f1cc4 in execute (op_array=0x816c670) at ./zend_execute.c:1605
#4  0x080f1e06 in execute (op_array=0x816c530) at ./zend_execute.c:1638
#5  0x080f1e06 in execute (op_array=0x816c278) at ./zend_execute.c:1638
#6  0x080f1e06 in execute (op_array=0x8166eec) at ./zend_execute.c:1638
#7  0x080d7b93 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at zend.c:810
#8  0x0805ea75 in php_execute_script (primary_file=0xb650) at main.c:1310
#9  0x0805cdb3 in main (argc=2, argv=0xb6fc) at cgi_main.c:753
#10 0x400c91be in __libc_start_main (main=0x805c580 , argc=2, ubp_av=0xb6fc,
   init=0x805b080 <_init>, fini=0x80f67b4 <_fini>, rtld_fini=0x4000ddd0 
<_dl_fini>,
   stack_end=0xb6ec) at ../sysdeps/generic/libc-start.c:129
(gdb) frame 3
#3  0x080f1cc4 in execute (op_array=0x816c670) at ./zend_execute.c:1605
(gdb) print (char 
*)(executor_globals.function_state_ptr->function)->common.function_name
$14 = 0x80fa6fa "pg_result_error"
(gdb) print (char *)executor_globals.active_op_array->function_name
$15 = 0x816cfc4 "result_error"
(gdb) print (char *)executor_globals.active_op_array->filename
$16 = 0x816afbc "/home/yohgaki/cvs/php/DEV/segfault.php"
(gdb)


The instruction in the url should be enough to get info needed.
Once you get function name and file name caused the segfault,
it should be easy to write short script reproduce the segfault.

--
Yasuo Ohgaki


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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=0x83476e4)
at /home/jan/software/php4/Zend/zend_alloc.c:229
#1  0x405664a1 in _zval_dtor (zvalue=0x83456bc)
at /home/jan/software/php4/Zend/zend_variables.c:44
#2  0x4055e4c1 in _zval_ptr_dtor (zval_ptr=0x40605714)
at /home/jan/software/php4/Zend/zend_execute_API.c:293
#3  0x4057516d in execute (op_array=0x835c0c4)
at /home/jan/software/php4/Zend/zend_execute_locks.h:26
#4  0x4057a30e in execute (op_array=0x836122c)
at /home/jan/software/php4/Zend/zend_execute.c:1641
#5  0x4057a30e in execute (op_array=0x82ae00c)
at /home/jan/software/php4/Zend/zend_execute.c:1641
#6  0x4057a30e in execute (op_array=0x81592c4)
at /home/jan/software/php4/Zend/zend_execute.c:1641
#7  0x40567c83 in zend_execute_scripts (type=8, retval=0x0, file_count=3)
at /home/jan/software/php4/Zend/zend.c:839
#8  0x4053d806 in php_execute_script (primary_file=0xb2a8)
at /home/jan/software/php4/main/main.c:1542
#9  0x40580b5e in apache_php_module_main (r=0x8142278, display_source_mode=0)
at /home/jan/software/php4/sapi/apache/sapi_apache.c:55
#10 0x4058174f in send_php (r=0x8142278, display_source_mode=0, filename=0x0)
at /home/jan/software/php4/sapi/apache/mod_php4.c:564
#11 0x405817b5 in send_parsed_php (r=0x8142278)
at /home/jan/software/php4/sapi/apache/mod_php4.c:579
#12 0x08054ad8 in ap_invoke_handler ()
#13 0x080677bc in ap_some_auth_required ()
#14 0x08067832 in ap_process_request ()
#15 0x0805fb29 in ap_child_terminate ()
#16 0x0805fcd8 in ap_child_terminate ()
#17 0x0805fe2d in ap_child_terminate ()
#18 0x0806047a in ap_child_terminate ()
#19 0x08060d15 in main ()
#20 0x401649ed in __libc_start_main () from /lib/libc.so.6

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft

-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Yasuo Ohgaki]

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/bugs-generating-backtrace.php

BTW, I wrote this pages months ago. (We're better to move the back
trace generating page more obvious place)

--
Yasuo Ohgaki

> 
> At 18:37 07/10/2002, Jan Schneider wrote:
> 
>> 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 
>> To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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 
>>this loop happens - beside a call to imap_utf7_decode() that wasn't 
>>called in the the first script - only some assignments and string and 
>>array functions.
>>
>>So I guess this actually has something to do with the engine.
>>
>>
>
>If you are on linux, you can try valgrind 
>(http://developer.kde.org/~sewardj/) like this:
>
>(first stop httpd)
>valgrind --gdb-attach /path/to/httpd -X
>
>then request your script and check the valgrind console window.
>It asks to attach when something goes wrong, press "Y" and then "bt" 
>from gdb. This should give a good understanding where it goes wrong.
>  
>
I'd like to but I get an "unhandled syscall: 197" though I don't even 
have such a call in unistd.h. :-(




-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Derick Rethans]

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 to imap_utf7_decode() that wasn't 
> called in the the first script - only some assignments and string and 
> array functions.
> 
> So I guess this actually has something to do with the engine.

If you are on linux, you can try valgrind 
(http://developer.kde.org/~sewardj/) like this:

(first stop httpd)
valgrind --gdb-attach /path/to/httpd -X

then request your script and check the valgrind console window.
It asks to attach when something goes wrong, press "Y" and then "bt" 
from gdb. This should give a good understanding where it goes wrong.

Derick

--

---
 Derick Rethans   http://derickrethans.nl/ 
 JDI Media Solutions
--[ if you hold a unix shell to your ear, do you hear the c? ]-


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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.
>
> PHP segfaults while returning from a function call. If I exit the 
> script before that call all is well. After the call I get the segfault.
> If I exit the script inside the function call directly _before_ the 
> function returns all is well again. This not a very complicated 
> function (a static method to be exact) and just returns a not very 
> long string by value.

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 to imap_utf7_decode() that wasn't 
called in the the first script - only some assignments and string and 
array functions.

So I guess this actually has something to do with the engine.




-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Vergoz Michael \(SYSDOOR\)]

hmm,

I think that this functionS is not free before the exit, and it take a
segfault.
Or perhaps the returned value are not free, and now it can be dengerous
!?@#! ?

Michael

- Original Message -
From: "Jan Schneider" <[EMAIL PROTECTED]>
To: "Zeev Suraski" <[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 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 from a function call. If I exit the script
> before that call all is well. After the call I get the segfault.
> If I exit the script inside the function call directly _before_ the
> function returns all is well again. This not a very complicated function
> (a static method to be exact) and just returns a not very long string by
> value.
>
>
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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 from a function call. If I exit the script 
before that call all is well. After the call I get the segfault.
If I exit the script inside the function call directly _before_ the 
function returns all is well again. This not a very complicated function 
(a static method to be exact) and just returns a not very long string by 
value.




-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Vergoz Michael \(SYSDOOR\)]

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


> 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 bytes
> >
> >I can understand him well ;-)
> >
> >BT:
> >
> >Program received signal SIGSEGV, Segmentation fault.
> >0x400d1ab1 in __kill () from /lib/libc.so.6
> >(gdb) bt
> >#0  0x400d1ab1 in __kill () from /lib/libc.so.6
> >#1  0x4049945c in _emalloc () at /root/cvs/cvsphp/Zend/zend_alloc.c:560
> >#2  0x404aad27 in concat_function ()
> >at /root/cvs/cvsphp/Zend/zend_operators.c:507
> >#3  0x404bfda5 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
> >#4  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
> >#5  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
> >#6  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
> >#7  0x404c4fb6 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
> >#8  0x404af654 in zend_execute_scripts () at
/root/cvs/cvsphp/Zend/zend.c:377
> >#9  0x40473ce5 in php_execute_script () at
/root/cvs/cvsphp/main/main.c:1455
> >#10 0x404c8110 in apache_php_module_main ()
> >at /root/cvs/cvsphp/sapi/apache/sapi_apache.c:65
> >#11 0x404c9138 in send_php (r=0x816f7a8, display_source_mode=0,
> >filename=0x81715a8
"/usr/local/httpd/htdocs/headhorde/imp/folders.php")
> >at /root/cvs/cvsphp/sapi/apache/mod_php4.c:564
> >#12 0x404c91c3 in send_parsed_php (r=0x816f7a8)
> >at /root/cvs/cvsphp/sapi/apache/mod_php4.c:579
> >#13 0x8055250 in ap_invoke_handler ()
> >#14 0x806791c in ap_some_auth_required ()
> >#15 0x8067993 in ap_process_request ()
> >#16 0x805fde7 in ap_child_terminate ()
> >#17 0x805ff95 in ap_child_terminate ()
> >#18 0x80600d6 in ap_child_terminate ()
> >#19 0x80606e8 in ap_child_terminate ()
> >#20 0x8060f55 in main ()
> >#21 0x400cba8e in __libc_start_main () at
../sysdeps/generic/libc-start.c:93
> >
> >
> >
> >--
> >PHP Development Mailing List <http://www.php.net/>
> >To unsubscribe, visit: http://www.php.net/unsub.php
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Zeev Suraski]

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?
>
>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 
>To unsubscribe, visit: http://www.php.net/unsub.php


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Jan Schneider]

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 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Segfaults in Zend

[Zeev Suraski]

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 bytes
>
>I can understand him well ;-)
>
>BT:
>
>Program received signal SIGSEGV, Segmentation fault.
>0x400d1ab1 in __kill () from /lib/libc.so.6
>(gdb) bt
>#0  0x400d1ab1 in __kill () from /lib/libc.so.6
>#1  0x4049945c in _emalloc () at /root/cvs/cvsphp/Zend/zend_alloc.c:560
>#2  0x404aad27 in concat_function ()
>at /root/cvs/cvsphp/Zend/zend_operators.c:507
>#3  0x404bfda5 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
>#4  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
>#5  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
>#6  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
>#7  0x404c4fb6 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
>#8  0x404af654 in zend_execute_scripts () at /root/cvs/cvsphp/Zend/zend.c:377
>#9  0x40473ce5 in php_execute_script () at /root/cvs/cvsphp/main/main.c:1455
>#10 0x404c8110 in apache_php_module_main ()
>at /root/cvs/cvsphp/sapi/apache/sapi_apache.c:65
>#11 0x404c9138 in send_php (r=0x816f7a8, display_source_mode=0,
>filename=0x81715a8 "/usr/local/httpd/htdocs/headhorde/imp/folders.php")
>at /root/cvs/cvsphp/sapi/apache/mod_php4.c:564
>#12 0x404c91c3 in send_parsed_php (r=0x816f7a8)
>at /root/cvs/cvsphp/sapi/apache/mod_php4.c:579
>#13 0x8055250 in ap_invoke_handler ()
>#14 0x806791c in ap_some_auth_required ()
>#15 0x8067993 in ap_process_request ()
>#16 0x805fde7 in ap_child_terminate ()
>#17 0x805ff95 in ap_child_terminate ()
>#18 0x80600d6 in ap_child_terminate ()
>#19 0x80606e8 in ap_child_terminate ()
>#20 0x8060f55 in main ()
>#21 0x400cba8e in __libc_start_main () at ../sysdeps/generic/libc-start.c:93
>
>
>
>--
>PHP Development Mailing List 
>To unsubscribe, visit: http://www.php.net/unsub.php


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Segfaults in Zend

[Jan Schneider]

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.
0x400d1ab1 in __kill () from /lib/libc.so.6
(gdb) bt
#0  0x400d1ab1 in __kill () from /lib/libc.so.6
#1  0x4049945c in _emalloc () at /root/cvs/cvsphp/Zend/zend_alloc.c:560
#2  0x404aad27 in concat_function ()
at /root/cvs/cvsphp/Zend/zend_operators.c:507
#3  0x404bfda5 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
#4  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
#5  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
#6  0x404c2e5c in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
#7  0x404c4fb6 in execute () at /root/cvs/cvsphp/Zend/zend_execute.c:963
#8  0x404af654 in zend_execute_scripts () at 
/root/cvs/cvsphp/Zend/zend.c:377
#9  0x40473ce5 in php_execute_script () at /root/cvs/cvsphp/main/main.c:1455
#10 0x404c8110 in apache_php_module_main ()
at /root/cvs/cvsphp/sapi/apache/sapi_apache.c:65
#11 0x404c9138 in send_php (r=0x816f7a8, display_source_mode=0,
filename=0x81715a8 "/usr/local/httpd/htdocs/headhorde/imp/folders.php")
at /root/cvs/cvsphp/sapi/apache/mod_php4.c:564
#12 0x404c91c3 in send_parsed_php (r=0x816f7a8)
at /root/cvs/cvsphp/sapi/apache/mod_php4.c:579
#13 0x8055250 in ap_invoke_handler ()
#14 0x806791c in ap_some_auth_required ()
#15 0x8067993 in ap_process_request ()
#16 0x805fde7 in ap_child_terminate ()
#17 0x805ff95 in ap_child_terminate ()
#18 0x80600d6 in ap_child_terminate ()
#19 0x80606e8 in ap_child_terminate ()
#20 0x8060f55 in main ()
#21 0x400cba8e in __libc_start_main () at 
../sysdeps/generic/libc-start.c:93



-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php