Opened 13 years ago

Closed 13 years ago

#3930 closed defect (fixed)

Segmentation fault for $map->extent request

Reported by: armin Owned by: aboudreault
Priority: high Milestone:
Component: MapScript-PHP Version: 6.0
Severity: normal Keywords: segmentation fault
Cc:

Description

I get a segmentation fault for MapServer 6.0 and PHP MapScript when applying

$map->extent;

System was Debian 4.0, PHP 5.2.17, MS 6.0.0

I stripped down the code to the minimum, it was always the "$map->extent" that produced the segfault. It didn't matter which extent and units I used in the map file. Running the same code with MS 5.6.6 works ok.

MAP
  EXTENT 5 40 20 60   
  UNITS dd 
  SIZE 500 500
END  

and

$mapfile = "test.map";
$map = ms_newMapObj($mapfile);
$maxextent = $map->extent;

I tried to produce a gdb backtrace:

# gdb /usr/local/bin/php core
GNU gdb 6.4.90-debian
...
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

Cannot access memory at address 0xb7f664e8
(gdb) bt
#0  _zval_ptr_dtor (zval_ptr=Cannot access memory at address 0xbfc15040
) at /home/install/mapserver/php-5.2.17/Zend/zend_execute_API.c:412
Cannot access memory at address 0xbfc1503c

Change History (3)

comment:1 by regiodata, 13 years ago

Priority: normalhigh

Had the same experience on my Debian 5.0 box. There were also segmentation faults with other complex Objects like:

$dummy = $map->extent;
$dummy = $map->legend;
...

Nevertheless simple attributes like "shapepath" worked.

Now with Debian 6.0 it works!

comment:2 by aboudreault, 13 years ago

I reproduced the bug building the extension with php 5.2.8. I will investigate in this.

comment:3 by aboudreault, 13 years ago

Resolution: fixed
Status: newclosed

Fixed and committed in trunk (r12077) and backported in branch 6.0 (r12078).

Note: See TracTickets for help on using tickets.