Your module is probably causing some memory corruption. The best way to
debug it is building the module statically into PHP. You need to copy it to
ext/your_module/ (assuming you have a standard config.m4).
Then in php4/ run ./buildconf and you should see your module when you do
./configure --help.
./configure and compile PHP with your module statically (best is even as a
CGI) and then you can really debug it and see if it's a problem with the
build as a shared library or if you have some bugs.
Andi
At 11:01 AM 4/30/2001 -0500, Brian Foddy wrote:
>Andi Gutmans wrote:
> >
> > Did you compile with debug on or off?
> > Please try without debug in both PHP and your module and let us know if
> > something changes.
> > Also can you try and load it via php.ini (extension=module.so) and not with
> > dl().
> >
>
>
>I rebuilt php 4.0.4p1 with debug off, rebuilt my module with debug off,
>and switched from using DL to the extension load in the php.ini.
>Unfortunately I still get the same coredump at the same line, just
>a different constant.
>
>As before I can step though it with the debugger and the address
>it cores in is viewable and has data.
>
>My gut is telling me its a build problem. Some address not aligned
>right or something. For example shouldn't the -KPIC have been
>used in the build argument list to libtool?
>
>But yet, in a seperate install without my new module the
>same version of php on the same machine is running in production
>very stable.
>
>Any ideas?
>Brian
>
>--
>PHP Development Mailing List <http://www.php.net/>
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
