Re: FreeBSD/Alpha Debugging Help Needed

Melvyn Sopacua wrote:

Hmm. Cores are rerouted through syslog. Can you find an entry in /etc/syslog.conf that would match it? Just add '*' to the list of destinations, so it gets 'walled'. Enable mesg -y though.

I'm about to give up. I get this in syslog: Oct 31 11:13:20 sticky /kernel: pid 39069 (php), uid 0: exited on signal 11 (core dumped) So I look at the make test window: pid 39067 (php): unaligned access: va=0x12023ebbc pc=0x120191374 ra=0x120191368 op=stq pid 39067 (php): unaligned access: va=0x12023eadc pc=0x120191374 ra=0x120191368 op=stq pid 39069 (php): unaligned access: va=0x12023ebbc pc=0x120191374 ra=0x120191368 op=stq pid 39069 (php): unaligned access: va=0x12023eadc pc=0x120191374 ra=0x120191368 op=stq FAIL HTML input/output [ext/mbstring/tests/htmlent.phpt] Found it, right? No. sticky# gdb sapi/cli/php GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd"... (gdb) (gdb) set args -f ext/mbstring/tests/htmlent.phpt (gdb) run Starting program: /usr/local/src/php-4.3.0pre2/sapi/cli/php -f ext/mbstring/tests/htmlent.phpt pid 39088 (php): unaligned access: va=0x12023ebbc pc=0x120191374 ra=0x120191368 op=stq pid 39088 (php): unaligned access: va=0x12023eadc pc=0x120191374 ra=0x120191368 op=stq --TEST-- HTML input/output --SKIPIF-- --INI-- output_handler = mb_output_handler zlib.output_compression = Off arg_separator.input="x" error_reporting=0 mbstring.http_input=HTML-ENTITIES mbstring.internal_encoding=UTF8 mbstring.http_output=HTML-ENTITIES mbstring.encoding_translation=On --FILE--

ISO-8859-1>pass test=''--EXPECT--

HTML-ENTITIES>UTF-8>HTML-ENTITIES test='&&;&@AB€‚äöü€⟨⟩' Program exited normally. (gdb) But, I have a core file to look at, right? sticky# gdb GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd". (gdb) target core php.core Core was generated by `php'. Program terminated with signal 11, Segmentation fault. warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x120029a08 This warning occurs if you are debugging a function without any symbols (for example, in a stripped executable). In that case, you may wish to increase the size of the search with the `set heuristic-fence-post' command. Otherwise, you told GDB there was a function where there isn't one, or (more likely) you have encountered a bug in GDB. #0 0x120029a08 in ?? () (gdb) bt #0 0x120029a08 in ?? () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x12002fa7c (gdb) Looks like gdb is hitting a fence and so am I. I'm not familar with debugging 64-bit issues at all... I guess I'm going to have to leave it to someone with more experence than I.

That has been failing on 64-bit archs, a long time now :(

I guess it would be safe to label PHP 4.3.0 as "unsafe for 64-bit platforms!"? :( - Matt