ID:               22513
 Updated by:       [EMAIL PROTECTED]
 Reported By:      jeremy at nirvani dot net
-Status:           Open
+Status:           Feedback
 Bug Type:         GD related
 Operating System: linux 2.4.19
 PHP Version:      5CVS-2003-03-03 (dev)
 New Comment:

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip




Previous Comments:
------------------------------------------------------------------------

[2003-06-03 10:06:02] veronique at talafone dot com

I have the latest PHP build (4.3.2, 29-May-2003), running Apache 2 on
Redhat 8.0, and I am still experiencing this bug. My configure line is
as follows:

'./configure' '--with-apxs2=/usr/local/apache2/current/bin/apxs'
'--with-mysql=/usr/local/mysql' '--with-zlib-dir=/usr/lib/'
'--enable-versioning' '--enable-track-vars=yes' '--enable-url-includes'
'--enable-sysvshm=yes' '--enable-sysvsem=yes' '--enable-ftp'
'--with-config-file-path=/etc' '--with-gettext=/usr/local' '--with-gd'
'--with-jpeg-dir=/usr/local/lib' '--with-imap=/usr/local/imap-2002c1'
'--with-imap-ssl=/usr/local/openssl' '--with-pear'
'--enable-gd-native-ttf' '--with-ttf' 

A print_r of the array returned by the function gives me something like
this:
Array ( [0] => 1108521344 [1] => 138256048 [2] => -1073758568 [3] =>
1075360060 [4] => 1108521360 [5] => 1108517584 [6] => -1073758536 [7]
=> 1107767671 )

------------------------------------------------------------------------

[2003-03-03 13:36:21] jeremy at nirvani dot net

Yes, as you may know, thttpd is not a threaded web server.

Jeremy

------------------------------------------------------------------------

[2003-03-03 13:33:51] [EMAIL PROTECTED]

You may experience problems if you use freetype in threaded enviroment,
since that library is not thread-safe. But that does not affect thttpd
afaik.

------------------------------------------------------------------------

[2003-03-03 13:21:50] jeremy at nirvani dot net

Without calculating what exactly it should show back, your example is
probably correct (as my build does not work, so I don't know exactly).

I have no idea why the build I am using is returning bogus data.  Does
it have something to do with using the thttpd sapi (I hope not) - as I
would hope that the gd_functions were abstracted enough to not be
interfered by a particular sapi implementation.  

I assume (as most bugs go) that if I were running this on Apache1,
there would be no problem - because I have never seen this problem on
apache1+php, but was shocked when it occured using thttpd+php. 
However, in theory, should this break with a particular sapi?  I mean,
what if this doesn't work with php-cgi or php, roxen, or apache2?  Do
we just say who cares, run apache1, or do we try and fix it?

I can run anything else anyone needs me to to try and get to the bottom
of this - just let me know.

Back to what is expected:
as the man page (http://php.net/imagettfbbox) says, those array
elements from 0->7 are positions of the image (X,Y) at the corners - so
the values I am getting are obviously wrong - and the ones you are
getting are what I would expect to see.  Any number over 1000 (positive
or negative) would seem to indicate something wrong.  If you look at
the values in the page I posted, you will see some really strange
numbers - almost like the pointers are getting printed, or something -
but anything but the correct values.

Jeremy

------------------------------------------------------------------------

[2003-03-03 13:07:59] [EMAIL PROTECTED]

Can you show that is the 'expected' output of this function?

On my system it returns
array(8) {
  [0]=>
  int(-3)
  [1]=>
  int(1)
  [2]=>
  int(79)
  [3]=>
  int(1)
  [4]=>
  int(79)
  [5]=>
  int(-34)
  [6]=>
  int(-3)
  [7]=>
  int(-34)
}

But since no position for the text is provided the positioning is
completely random. What matters is the difference between the various
numbers, which you can use to determine the how much space the text
will occupy.

------------------------------------------------------------------------

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/22513

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

Reply via email to