Date: 11/25/99
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2700 Updated: include/require paths different"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2707 Updated: Weird POST problem"
- In reply to: Bill Spornitz: "[PHP-DEV] backtrace from segmentation fault"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Which version of Apache?
Whenever I see an _IO_* function in a core dump, I immediately suspect the
linking problem that was present in all versions of Apache up to
1.3.9. So, if you are not using Apache-1.3.9, please upgrade and try
again. Even if you are, make very sure that the apxs script you are
running the PHP configure against is the one that came from your 1.3.9
install. The think to look for the that it uses "gcc -shared" to link as
opposed to "ld -Bshareable".
Chances are this isn't the problem in this case. And I also don't quite
understand this backtrace. How did _php3_parse_gpc_data() end up calling
PQdisplayTuples()?
-Rasmus
On Thu, 25 Nov 1999, Bill Spornitz wrote:
> I'm having a problem with the discussion group software Phorum. After
> following instructions in the php faq, I'm including the backtrace from the
> segmentaion fault. Here it is:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x4 in ?? () from /lib/libresolv.so.2
> (gdb) bt
> #0 0x4 in ?? () from /lib/libresolv.so.2
> #1 0x400e2856 in _IO_vfprintf (s=0x40186500, format=0x4029cba8 "%s",
> ap=0xbfffea8c)
> at vfprintf.c:1018
> #2 0x400ea6f7 in fprintf (stream=0x40186500, format=0x4029cba8 "%s") at
> fprintf.c:32
> #3 0x40297c5d in pqGetInt ()
> #4 0x40298b57 in PQdisplayTuples ()
> #5 0x4029818e in pqWait ()
> #6 0x402989be in PQprint ()
> #7 0x40298af0 in PQdisplayTuples ()
> #8 0x40241894 in _php3_parse_gpc_data (val=0x80e4cd0 "\005",
> var=0x40291c34 "\004",
> track_vars_array=0x40293088) at functions/post.c:360
> #9 0x4025f4f7 in phpparse () at control_structures_inline.h:1276
> #10 0x4022319e in add_function (result=0x80cda70, op1=0x4028018c, op2=0x13)
> at operators.c:319
> #11 0x4022347c in mul_function (result=0x80c4d9c, op1=0x13, op2=0x0) at
> operators.c:423
> #12 0x402205d5 in php3_config_ini_startup () at main.c:1097
> #13 0x4022064f in php3_config_ini_startup () at main.c:1107
> #14 0x805292e in ap_invoke_handler ()
> #15 0x806065b in ap_some_auth_required ()
> #16 0x80606b8 in ap_process_request ()
> #17 0x805a818 in ap_child_terminate ()
> #18 0x805a957 in ap_child_terminate ()
> #19 0x805aa58 in ap_child_terminate ()
> #20 0x805af08 in ap_child_terminate ()
> #21 0x805b4fb in main ()
> #22 0x400b5cb3 in __libc_start_main (main=0x805b290 <main>, argc=4,
> argv=0xbffffd38,
> init=0x804e684 <_init>, fini=0x80794ec <_fini>, rtld_fini=0x4000a350
> <_dl_fini>,
> stack_end=0xbffffd34) at ../sysdeps/generic/libc-start.c:78
>
> Any help would be appreciated.
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2700 Updated: include/require paths different"
- Previous message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #2707 Updated: Weird POST problem"
- In reply to: Bill Spornitz: "[PHP-DEV] backtrace from segmentation fault"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

