[FX.php List] malloc errror from fx.php with PHP5 on Mac OS X Server

[Steve Hannah]

I am running the same Marc Liyanage install of PHP 5 on OS X (10.4.3)  
(not server), and have received this error on some other occasions  
with various PHP scripts also.  I have not been able to solve this  
problem.  In all cases, the errors are not reproducable on any other  
installations that I have run across (including PHP 4 on Apache 1.33  
on OS X, ...) , so I decided that it was a problem with the Marc  
Liyange build (probably a conflict with one one of the modules he has  
loaded with it).

-Steve Hannah

On 30-Jan-06, at 2:03 PM, David Milley wrote:

> I've encountered a problem using fx.php with PHP5 on Mac OS X Server
> that I can't seem to find documentation to solve. I've been developing
> an in-house application using PHP 4.3.11, but an incoming vendor
> application requires the PHP5 XML libraries, so I need to make the  
> move
> to 5.
>
> Standard fx.php code causes the problem:
>
> $person = '1234';
> $handle = new FX('XXX.XXX.XXX.XXX', '80', 'FMPro7');
> $handle->SetDBData("database.fp7", "web_layout");
> $handle->SetDBUserPass ( "SpecialAccount", "SpecialAccountPassword");
> $handle->AddDBParam("Name", $person);
> $handledata=$handle->FMFind();
>
> produces this result:
>
> *** malloc[17638]: Deallocation of a pointer not malloced: 0x213158c;
> This could be a double free(), or free() called with the middle of an
> allocated block; Try setting environment variable MallocHelp to see
> tools to help debug
> [Thu Jan 19 16:32:47 2006] [notice] child pid 17638 exit signal
> Segmentation fault (11)
>
> Tracking through the code line-by-line, I've found that it's the
> FMFind() line that throws the error -- as does FMFindall and the rest.
>
> I'm using the Marc Liyanage install of PHP 5.0.4 on Mac OS X Server
> running Apache 1.3.33.
>
> I've tested these files using PHP 5.0.4 on Mac OS X (not Server)
> running Apache 1.3.33, with no problem  -- also no problem running on
> Win2000 with PHP 5.04 and Apache 1.3.33.
>
> I'll admit to being mystified, particularly since this problem only
> arises (so far) in this configuration when I try to use fx.php.  Other
> PHP apps seem unaffected.
>
> Any help would be welcome.
>
> Dave
> -- 
> David Milley, Web Technical Developer
> Stokes Research Institute, Children's Hospital of Philadelphia
> ext: 215-590-1197 / int: 41197
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>