#37236 [Com]: Function move_uploaded_file(): canot work in snap 200604281030

2006-05-09 Thread 0602 at eq dot cz
 ID:   37236
 Comment by:   0602 at eq dot cz
 Reported By:  youza at post dot cz
 Status:   Assigned
 Bug Type: *Directory/Filesystem functions
 Operating System: fedora core 4
 PHP Version:  4CVS-2006-04-28 (snap)
 Assigned To:  pollita
 New Comment:

Hi, the same here with 5.1.4. The problem in 5.1.4 sources is here:
http://cvs.php.net/viewcvs.cgi/php-src/ext/standard/file.c?r1=1.409.2.5r2=1.409.2.6
- commited by iliaa. When 'upload_tmp_dir' is on a different filesystem
then the destination file, the code in move_uploaded_file fails on
rename and then tries php_copy_file, which after the iliaa's commit
checks also the source path for open_basedir restriction. The obvious
workaround for this bug is to reconfigure upload_tmp_dir to be on the
same fs as the destination.


Previous Comments:


[2006-04-28 11:31:25] youza at post dot cz

Description:

Function move_uploaded_file()  work fine in
php4-STABLE-200602010935.tar.gz

but not work in last php4-STABLE-200604281030.tar.gz
the code www page, directory structure and permission  and apache,
configuration is the same.

Error message:

[28-Apr-2006 12:28:16] PHP Warning:  move_uploaded_file(): open_basedir
restriction in effect. File(/tmp/php0FDyAV) is not within the allowed
path(s): (/my/web/path) in /my/web/path/upload/upload.php on line 53
[28-Apr-2006 12:28:16] PHP Warning: 
move_uploaded_file(/tmp/php0FDyAV): failed to open stream: Operation
not permitted in /my/web/path/upload/upload.php on line 53
[28-Apr-2006 12:28:16] PHP Warning:  move_uploaded_file(): Unable to
move '/tmp/php0FDyAV' to 'upload/php0FDyAV' in
/my/web/path/upload/upload.php on line 53

How is problem  in  ext/standard/file.c ???

the chages:
http://cvs.php.net/viewcvs.cgi/php-src/ext/standard/file.c?r1=1.279.2.70.2.6r2=1.279.2.70.2.7pathrev=PHP_4_4



Reproduce code:
---
move_uploaded_file($file, $destination);






-- 
Edit this bug report at http://bugs.php.net/?id=37236edit=1


#35216 [NEW]: segfault using db3

2005-11-14 Thread 0602 at eq dot cz
From: 0602 at eq dot cz
Operating system: Linux
PHP version:  4.4.1
PHP Bug Type: Reproducible crash
Bug description:  segfault using db3

Description:

Segfault using db3 with php version 4.4.1 (and snapshot
php4-STABLE-200511141355) as module for apache (no problems with cli).

Reproduce code:
---
?
$db = 'data/hereshow.db';
$id = dba_open($db, 'n', 'db3');
if(!$id) {
exit('Could not open database '.$db);
}

$key = time();
if(!dba_insert($key, 'Time in seconds', $id)) {
dba_close($id);
exit('Could not update database'.$db);
}
else {
echo 'Successfully updated database with key =
'.$key.'br/';
}

if(($value = dba_fetch($key,$id))) {
echo 'Found key '.$key.' with value '.$value.'br/';
}
else {
echo 'Could not find key '.$key.'br/';
}

dba_close($id);
?


Expected result:

Correct hereshow.db db file in data directory.

Actual result:
--
The file hereshow.db is created and is empty (size 0). The process
segfaults. The backtrace is the same for 4.4.1 and 200511141355:

(gdb) bt
#0  0x00317a7b in __dbenv_get_errfile () from /lib/libdb-4.2.so
#1  0x00308bf9 in __dbh_am_chk () from /lib/libdb-4.2.so
#2  0x006848b8 in dba_open_db3 () from /usr/local/lib/php/libphp4.so
#3  0x00681f7f in php_dba_find () from /usr/local/lib/php/libphp4.so
#4  0x00682aec in zif_dba_open () from /usr/local/lib/php/libphp4.so
#5  0x00806d87 in execute () from /usr/local/lib/php/libphp4.so
#6  0x007f388f in zend_execute_scripts () from
/usr/local/lib/php/libphp4.so
#7  0x007be18f in php_execute_script () from
/usr/local/lib/php/libphp4.so
#8  0x0080ccc6 in execute () from /usr/local/lib/php/libphp4.so
#9  0x08068026 in ap_run_handler (r=0x819e170) at config.c:152
#10 0x080685c8 in ap_invoke_handler (r=0x819e170) at config.c:364
#11 0x0806554f in ap_process_request (r=0x819e170) at http_request.c:249
#12 0x08060ec9 in ap_process_http_connection (c=0x8198078) at
http_core.c:251
#13 0x08071186 in ap_run_process_connection (c=0x8198078) at
connection.c:43
#14 0x080669d8 in child_main (child_num_arg=6833920) at prefork.c:610
#15 0x08066b8e in make_child (s=0x80a0ed0, slot=0) at prefork.c:650
#16 0x08066bff in startup_children (number_to_start=1) at prefork.c:722
#17 0x08067379 in ap_mpm_run (_pconf=0x809f0f0, plog=0x80cb1a0, s=0x1) at
prefork.c:941
#18 0x0806cbc8 in main (argc=2, argv=0xbfffdbb4) at main.c:618

# ldd httpd 
[...]
libdb-4.2.so = /lib/libdb-4.2.so (0x00289000)
[...]

# ldd libphp4.so
[...]
libdb-3.3.so = /lib/libdb-3.3.so (0x00761000)
[...]

*NO* problems with the following httpd (different os version (older) -
httpd linked against different libdb; same version of apache and php on
both oses):
# ldd httpd
[...]
libdb-3.3.so = /lib/libdb-3.3.so (0x00275000)
[...]

PHP was configured with --with-db3. This libdb versions are installed on
affected system: db3-3.3.11, db4-4.2.52.


-- 
Edit bug report at http://bugs.php.net/?id=35216edit=1
-- 
Try a CVS snapshot (php4):   http://bugs.php.net/fix.php?id=35216r=trysnapshot4
Try a CVS snapshot (php5.0): 
http://bugs.php.net/fix.php?id=35216r=trysnapshot50
Try a CVS snapshot (php5.1): 
http://bugs.php.net/fix.php?id=35216r=trysnapshot51
Fixed in CVS:http://bugs.php.net/fix.php?id=35216r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=35216r=alreadyfixed
Need backtrace:  http://bugs.php.net/fix.php?id=35216r=needtrace
Need Reproduce Script:   http://bugs.php.net/fix.php?id=35216r=needscript
Try newer version:   http://bugs.php.net/fix.php?id=35216r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=35216r=support
Expected behavior:   http://bugs.php.net/fix.php?id=35216r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=35216r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=35216r=submittedtwice
register_globals:http://bugs.php.net/fix.php?id=35216r=globals
PHP 3 support discontinued:  http://bugs.php.net/fix.php?id=35216r=php3
Daylight Savings:http://bugs.php.net/fix.php?id=35216r=dst
IIS Stability:   http://bugs.php.net/fix.php?id=35216r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=35216r=gnused
Floating point limitations:  http://bugs.php.net/fix.php?id=35216r=float
No Zend Extensions:  http://bugs.php.net/fix.php?id=35216r=nozend
MySQL Configuration Error:   http://bugs.php.net/fix.php?id=35216r=mysqlcfg


#33758 [Bgs]: segfault in imap_mail_compose

2005-11-03 Thread 0602 at eq dot cz
 ID:   33758
 User updated by:  0602 at eq dot cz
 Reported By:  0602 at eq dot cz
 Status:   Bogus
 Bug Type: IMAP related
 Operating System: Slackware Linux
 PHP Version:  5CVS, 4CVS (2005-07-20)
 Assigned To:  iliaa
 New Comment:

Pathetic. Here is a patch to 4.4.1:
H4sICAkgakMCA2ltYXBfbWFpbF9jb21wb3NlLnBhdGNoAO1VTW/iMBA9p7/C6qEK
DW6dZIFSRAVCSHtAVUXaPezFchOXREs+5Bgou9r/viYx+VgSGqT21OYAyBm/mXlv
3gAhBPSVX3s+ia4jN8K7H1c2DJm3UAyEOlDXITKB3rk19VsTXaH9AzSkI3SmaVoV
QKO7oxGAxk3vpt0FWvLdA6PRGVDEY69iHvrYpcShLMYRYcQHQ+ATb4kDunkOnW16
SDllamsgb4XBmjKOeYhjzrxggemrSoM1dggnWVAFNLxbk+WKigyq7RIGLlvgJcYL
ytWf2Hqcz6b3+OEhRwIa0AWcVg9HuMj/vOI7yPun2Uzm9qlvR1v1SAltkGT8MZ6V
MsrjmkIS7N80cLBLYhf74Zril5BtCHNEA+P5Hi5KUrSOMxEIOUXV3I/Sk0GqUx/1
hT6a0ddRrlMl4TJLmiSDeVO9LDIXQ3AlYNUiI3kLsHynyPj55Pt4bk0fz1ONaqIk
ehZ8WIekQtQL77J606jyWZkv8f6vJE2XpBkF0pSN6y0pUHPBxKBhe8UYDXiia5Vo
baCuQ88Bl2I2LxwvjuQEDIfAeppMppbVAn9SfCV53dAzSnUZv+i2uooL8UZ8eoHT
BkjKUMxY5lgES5/UhkgZRGRWUuVY5T0PDtps5t8CawXf7E15gFa2Yn657MUD0FT4
jpkK3/n2JfwnEt5Eem8nvPgu/p0134JVa/BYa1KeYl+yrf+Byl1lstaDQaXxhj1x
xTbcsW8tWbllTWRIzo0i5x/vttPs9j5+a2K4UxzX1HLv5bmPMV1XTwega3wNwCcb
gH+EF9R8wgwAAA==

It's base64 from gzipped patch, I hope the web interface won't corrupt
it. Extract with e.g. 'echo -n THE_STRING | openssl base64 -d | zcat
 patchfile'.


Previous Comments:


[2005-07-21 01:41:41] 0602 at eq dot cz

Bug #32589 was reported 2.4.2005 - more then three months before 4.4.0
(11.7.2005) and I have very strong feeling that at the time I was
submitting this one, #32589 was marked as closed. It's good to know
that every record here marked closed should people consider
``existing''. Anyway - let's suppose that #32589 was marked as open at
the time I was submitting this one - is it a common practise to release
another _stable_ version when you know there is such a serious bug in
it?



[2005-07-20 20:55:19] [EMAIL PROTECTED]

Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. 

Thank you for your interest in PHP.

See bug #32589




[2005-07-19 21:18:30] [EMAIL PROTECTED]

Assigned to Ilia who said he could reproduce this.



[2005-07-19 02:19:22] 0602 at eq dot cz

The crash is reproducible with c-client from pine 4.62 and 4.63, build
script is similar to this one:
ftp://ftp.slackware.com/pub/slackware/slackware-current/source/n/php/php.SlackBuild
with the exception that I use apache2, i.e. different apxs. I don't get
the segfault with php 4.3.10 and c-client from pine 4.63.



[2005-07-19 00:07:00] [EMAIL PROTECTED]

I can not reproduce this. Exactly what c-client version are you
compiling PHP with? What configure line did you use?




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/33758

-- 
Edit this bug report at http://bugs.php.net/?id=33758edit=1


#33758 [Bgs]: segfault in imap_mail_compose

2005-07-20 Thread 0602 at eq dot cz
 ID:   33758
 User updated by:  0602 at eq dot cz
 Reported By:  0602 at eq dot cz
 Status:   Bogus
 Bug Type: IMAP related
 Operating System: Slackware Linux
 PHP Version:  5CVS, 4CVS (2005-07-20)
 Assigned To:  iliaa
 New Comment:

Bug #32589 was reported 2.4.2005 - more then three months before 4.4.0
(11.7.2005) and I have very strong feeling that at the time I was
submitting this one, #32589 was marked as closed. It's good to know
that every record here marked closed should people consider
``existing''. Anyway - let's suppose that #32589 was marked as open at
the time I was submitting this one - is it a common practise to release
another _stable_ version when you know there is such a serious bug in
it?


Previous Comments:


[2005-07-20 20:55:19] [EMAIL PROTECTED]

Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. 

Thank you for your interest in PHP.

See bug #32589




[2005-07-19 21:18:30] [EMAIL PROTECTED]

Assigned to Ilia who said he could reproduce this.



[2005-07-19 02:19:22] 0602 at eq dot cz

The crash is reproducible with c-client from pine 4.62 and 4.63, build
script is similar to this one:
ftp://ftp.slackware.com/pub/slackware/slackware-current/source/n/php/php.SlackBuild
with the exception that I use apache2, i.e. different apxs. I don't get
the segfault with php 4.3.10 and c-client from pine 4.63.



[2005-07-19 00:07:00] [EMAIL PROTECTED]

I can not reproduce this. Exactly what c-client version are you
compiling PHP with? What configure line did you use?




[2005-07-18 23:58:38] 0602 at eq dot cz

# gdb /usr/local/apache2/bin/httpd   
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for
details.
This GDB was configured as i386-slackware-linux...
(gdb) run -X
Starting program: /usr/local/apache2/bin/httpd -X
[New Thread 16384 (LWP 7894)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7894)]
0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x0047e880 in free () from /lib/libc.so.6
#2  0x00785bee in fs_give () from
/usr/local/apache2/modules/libphp4.so
#3  0x00795199 in mail_free_body_parameter () from
/usr/local/apache2/modules/libphp4.so
#4  0x00794f94 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#5  0x007951c5 in mail_free_body_part () from
/usr/local/apache2/modules/libphp4.so
#6  0x00795140 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#7  0x00794f4d in mail_free_body () from
/usr/local/apache2/modules/libphp4.so
#8  0x006540dc in zif_imap_mail_compose () from
/usr/local/apache2/modules/libphp4.so
#9  0x00774c60 in execute () from
/usr/local/apache2/modules/libphp4.so
#10 0x00761471 in zend_execute_scripts () from
/usr/local/apache2/modules/libphp4.so
#11 0x0072ca3c in php_execute_script () from
/usr/local/apache2/modules/libphp4.so
#12 0x0077ab2c in execute () from
/usr/local/apache2/modules/libphp4.so
#13 0x0806712a in ap_run_handler (r=0x822a7f0) at config.c:153
#14 0x08067642 in ap_invoke_handler (r=0x822a7f0) at config.c:364
#15 0x08064a3f in ap_process_request (r=0x822a7f0) at
http_request.c:249
#16 0x08060af9 in ap_process_http_connection (c=0x82248b0) at
http_core.c:251
#17 0x0806f3f6 in ap_run_process_connection (c=0x82248b0) at
connection.c:43
#18 0x08065ca3 in child_main (child_num_arg=3) at prefork.c:610
#19 0x08065e4e in make_child (s=0x809c340, slot=0) at prefork.c:650
#20 0x08065ea7 in startup_children (number_to_start=2) at
prefork.c:722
#21 0x080665b5 in ap_mpm_run (_pconf=0x806566c, plog=0x80c4638,
s=0x809c340) at prefork.c:941
#22 0x0806b56a in main (argc=2, argv=0xba24) at main.c:618
#23 0x0041ebb4 in __libc_start_main () from /lib/libc.so.6
(gdb)



The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/33758

-- 
Edit this bug report at http://bugs.php.net/?id=33758edit=1


#33758 [Fbk-Opn]: segfault in imap_mail_compose

2005-07-18 Thread 0602 at eq dot cz
 ID:   33758
 User updated by:  0602 at eq dot cz
 Reported By:  0602 at eq dot cz
-Status:   Feedback
+Status:   Open
 Bug Type: Reproducible crash
 Operating System: Slackware Linux
 PHP Version:  4.4.0
 New Comment:

# gdb /usr/local/apache2/bin/httpd   
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for
details.
This GDB was configured as i386-slackware-linux...
(gdb) run -X
Starting program: /usr/local/apache2/bin/httpd -X
[New Thread 16384 (LWP 7894)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7894)]
0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x0047e880 in free () from /lib/libc.so.6
#2  0x00785bee in fs_give () from
/usr/local/apache2/modules/libphp4.so
#3  0x00795199 in mail_free_body_parameter () from
/usr/local/apache2/modules/libphp4.so
#4  0x00794f94 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#5  0x007951c5 in mail_free_body_part () from
/usr/local/apache2/modules/libphp4.so
#6  0x00795140 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#7  0x00794f4d in mail_free_body () from
/usr/local/apache2/modules/libphp4.so
#8  0x006540dc in zif_imap_mail_compose () from
/usr/local/apache2/modules/libphp4.so
#9  0x00774c60 in execute () from
/usr/local/apache2/modules/libphp4.so
#10 0x00761471 in zend_execute_scripts () from
/usr/local/apache2/modules/libphp4.so
#11 0x0072ca3c in php_execute_script () from
/usr/local/apache2/modules/libphp4.so
#12 0x0077ab2c in execute () from
/usr/local/apache2/modules/libphp4.so
#13 0x0806712a in ap_run_handler (r=0x822a7f0) at config.c:153
#14 0x08067642 in ap_invoke_handler (r=0x822a7f0) at config.c:364
#15 0x08064a3f in ap_process_request (r=0x822a7f0) at
http_request.c:249
#16 0x08060af9 in ap_process_http_connection (c=0x82248b0) at
http_core.c:251
#17 0x0806f3f6 in ap_run_process_connection (c=0x82248b0) at
connection.c:43
#18 0x08065ca3 in child_main (child_num_arg=3) at prefork.c:610
#19 0x08065e4e in make_child (s=0x809c340, slot=0) at prefork.c:650
#20 0x08065ea7 in startup_children (number_to_start=2) at
prefork.c:722
#21 0x080665b5 in ap_mpm_run (_pconf=0x806566c, plog=0x80c4638,
s=0x809c340) at prefork.c:941
#22 0x0806b56a in main (argc=2, argv=0xba24) at main.c:618
#23 0x0041ebb4 in __libc_start_main () from /lib/libc.so.6
(gdb)


Previous Comments:


[2005-07-18 20:55:08] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php

Once you have generated a backtrace, please submit it to this bug
report and change the status back to Open. Thank you for helping
us make PHP better.



[2005-07-18 20:46:03] 0602 at eq dot cz

Description:

Whenever I run following code with imap_mail_compose() function,
something like this gets logged: [notice] child pid 11556 exit signal
Segmentation fault (11). Functions imap_listmailbox(), imap_headers()
and imap_open() are working fine.

Reproduce code:
---
?
$m_envelope[to] = [EMAIL PROTECTED];

$m_part1[type] = TYPEMULTIPART;
$m_part1[subtype] = mixed;

$m_part2[type] = TYPETEXT;
$m_part2[subtype] = plain;
$m_part2[charset] = WINDOWS-1250;
$m_part2[description] = text_message;
$m_part2[contents.data] = content;

$m_body[1] = $m_part1;
$m_body[2] = $m_part2;

$m_whole = IMAP_Mail_Compose($m_envelope,$m_body);
?







-- 
Edit this bug report at http://bugs.php.net/?id=33758edit=1


#33758 [NEW]: segfault in imap_mail_compose

2005-07-18 Thread 0602 at eq dot cz
From: 0602 at eq dot cz
Operating system: Slackware Linux
PHP version:  4.4.0
PHP Bug Type: Reproducible crash
Bug description:  segfault in imap_mail_compose

Description:

Whenever I run following code with imap_mail_compose() function, something
like this gets logged: [notice] child pid 11556 exit signal Segmentation
fault (11). Functions imap_listmailbox(), imap_headers() and imap_open()
are working fine.

Reproduce code:
---
?
$m_envelope[to] = [EMAIL PROTECTED];

$m_part1[type] = TYPEMULTIPART;
$m_part1[subtype] = mixed;

$m_part2[type] = TYPETEXT;
$m_part2[subtype] = plain;
$m_part2[charset] = WINDOWS-1250;
$m_part2[description] = text_message;
$m_part2[contents.data] = content;

$m_body[1] = $m_part1;
$m_body[2] = $m_part2;

$m_whole = IMAP_Mail_Compose($m_envelope,$m_body);
?



-- 
Edit bug report at http://bugs.php.net/?id=33758edit=1
-- 
Try a CVS snapshot (php4):   http://bugs.php.net/fix.php?id=33758r=trysnapshot4
Try a CVS snapshot (php5.0): 
http://bugs.php.net/fix.php?id=33758r=trysnapshot50
Try a CVS snapshot (php5.1): 
http://bugs.php.net/fix.php?id=33758r=trysnapshot51
Fixed in CVS:http://bugs.php.net/fix.php?id=33758r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=33758r=alreadyfixed
Need backtrace:  http://bugs.php.net/fix.php?id=33758r=needtrace
Need Reproduce Script:   http://bugs.php.net/fix.php?id=33758r=needscript
Try newer version:   http://bugs.php.net/fix.php?id=33758r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=33758r=support
Expected behavior:   http://bugs.php.net/fix.php?id=33758r=notwrong
Not enough info: 
http://bugs.php.net/fix.php?id=33758r=notenoughinfo
Submitted twice: 
http://bugs.php.net/fix.php?id=33758r=submittedtwice
register_globals:http://bugs.php.net/fix.php?id=33758r=globals
PHP 3 support discontinued:  http://bugs.php.net/fix.php?id=33758r=php3
Daylight Savings:http://bugs.php.net/fix.php?id=33758r=dst
IIS Stability:   http://bugs.php.net/fix.php?id=33758r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=33758r=gnused
Floating point limitations:  http://bugs.php.net/fix.php?id=33758r=float
No Zend Extensions:  http://bugs.php.net/fix.php?id=33758r=nozend
MySQL Configuration Error:   http://bugs.php.net/fix.php?id=33758r=mysqlcfg


#33758 [Fbk-Opn]: segfault in imap_mail_compose

2005-07-18 Thread 0602 at eq dot cz
 ID:   33758
 User updated by:  0602 at eq dot cz
 Reported By:  0602 at eq dot cz
-Status:   Feedback
+Status:   Open
 Bug Type: IMAP related
 Operating System: Slackware Linux
 PHP Version:  4.4.0
 New Comment:

The crash is reproducible with c-client from pine 4.62 and 4.63, build
script is similar to this one:
ftp://ftp.slackware.com/pub/slackware/slackware-current/source/n/php/php.SlackBuild
with the exception that I use apache2, i.e. different apxs. I don't get
the segfault with php 4.3.10 and c-client from pine 4.63.


Previous Comments:


[2005-07-19 00:07:00] [EMAIL PROTECTED]

I can not reproduce this. Exactly what c-client version are you
compiling PHP with? What configure line did you use?




[2005-07-18 23:58:38] 0602 at eq dot cz

# gdb /usr/local/apache2/bin/httpd   
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for
details.
This GDB was configured as i386-slackware-linux...
(gdb) run -X
Starting program: /usr/local/apache2/bin/httpd -X
[New Thread 16384 (LWP 7894)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7894)]
0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x003ba3bd in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x0047e880 in free () from /lib/libc.so.6
#2  0x00785bee in fs_give () from
/usr/local/apache2/modules/libphp4.so
#3  0x00795199 in mail_free_body_parameter () from
/usr/local/apache2/modules/libphp4.so
#4  0x00794f94 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#5  0x007951c5 in mail_free_body_part () from
/usr/local/apache2/modules/libphp4.so
#6  0x00795140 in mail_free_body_data () from
/usr/local/apache2/modules/libphp4.so
#7  0x00794f4d in mail_free_body () from
/usr/local/apache2/modules/libphp4.so
#8  0x006540dc in zif_imap_mail_compose () from
/usr/local/apache2/modules/libphp4.so
#9  0x00774c60 in execute () from
/usr/local/apache2/modules/libphp4.so
#10 0x00761471 in zend_execute_scripts () from
/usr/local/apache2/modules/libphp4.so
#11 0x0072ca3c in php_execute_script () from
/usr/local/apache2/modules/libphp4.so
#12 0x0077ab2c in execute () from
/usr/local/apache2/modules/libphp4.so
#13 0x0806712a in ap_run_handler (r=0x822a7f0) at config.c:153
#14 0x08067642 in ap_invoke_handler (r=0x822a7f0) at config.c:364
#15 0x08064a3f in ap_process_request (r=0x822a7f0) at
http_request.c:249
#16 0x08060af9 in ap_process_http_connection (c=0x82248b0) at
http_core.c:251
#17 0x0806f3f6 in ap_run_process_connection (c=0x82248b0) at
connection.c:43
#18 0x08065ca3 in child_main (child_num_arg=3) at prefork.c:610
#19 0x08065e4e in make_child (s=0x809c340, slot=0) at prefork.c:650
#20 0x08065ea7 in startup_children (number_to_start=2) at
prefork.c:722
#21 0x080665b5 in ap_mpm_run (_pconf=0x806566c, plog=0x80c4638,
s=0x809c340) at prefork.c:941
#22 0x0806b56a in main (argc=2, argv=0xba24) at main.c:618
#23 0x0041ebb4 in __libc_start_main () from /lib/libc.so.6
(gdb)



[2005-07-18 20:55:08] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php

Once you have generated a backtrace, please submit it to this bug
report and change the status back to Open. Thank you for helping
us make PHP better.



[2005-07-18 20:46:03] 0602 at eq dot cz

Description:

Whenever I run following code with imap_mail_compose() function,
something like this gets logged: [notice] child pid 11556 exit signal
Segmentation fault (11). Functions imap_listmailbox(), imap_headers()
and imap_open() are working fine.

Reproduce code:
---
?
$m_envelope[to] = [EMAIL PROTECTED];

$m_part1[type] = TYPEMULTIPART;
$m_part1[subtype] = mixed;

$m_part2[type] = TYPETEXT;
$m_part2[subtype] = plain;
$m_part2[charset] = WINDOWS-1250;
$m_part2[description] = text_message;
$m_part2[contents.data] = content;

$m_body[1] = $m_part1;
$m_body[2] = $m_part2;

$m_whole = IMAP_Mail_Compose($m_envelope,$m_body);
?







-- 
Edit this bug report at http://bugs.php.net/?id=33758edit=1