Edit report at https://bugs.php.net/bug.php?id=50660&edit=1
ID: 50660
Updated by: php-bugs@lists.php.net
Reported by: skinny dot bravo at gmail dot com
Summary: exif_read_data(): Illegal IFD offset (works fine with
other exif readers)
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: EXIF related
Operating System: Linux
PHP Version: 5.*, 6
Assigned To: kalle
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2016-08-05 18:31:02] support at imgsrc dot ru
Can you please try
http://o1.eu.is.pp.ru/v/vahmurka/3/16095163cDU.jpghttp://o1.eu.is.pp.ru/v/vahmurka/1/16095161rno.jpg
------------------------------------------------------------------------
[2016-08-05 06:13:26] kalle@php.net
Hi!
I know this is an old report, could you please reupload the images somewhere? For some reason my ISP
have blocked the domain and I do not have a way currently to obtain them from the outside.
thanks!
------------------------------------------------------------------------
[2011-01-31 07:36:37] mjk at emmjaykay dot org
The issue stems from exif.c's exif_process_IFD_in_JPEG() function where it calculates
NextDirOffset. If this means what I think it does, for EXIF_IFD and IFD_GPS, there is no next IFD
and no further parsing should take place. Right now, it parses into the string for the next entry
(2009...)
I am not sure if this is correct since I am no expert on EXIF.
The output of var_dump seems to be still in-correct, though. I do not know if this is a separate
issue or something I introduced with this patch.
------------------------------------------------------------------------
[2010-01-06 12:49:45] skinny dot bravo at gmail dot com
Sorry,
- php5.2-201001041530 produces the same result
+ php5.2-201001041530 produces the same result as 5.2.12 below
------------------------------------------------------------------------
[2010-01-06 12:42:40] iliaa@php.net
If it works with php5.2-201001041530 it means that the issue has been
resolved.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=50660
--
Edit this bug report at https://bugs.php.net/bug.php?id=50660&edit=1