Discussion:
test_format breaks when run in farm on hp/ux
Quest
2003-05-25 21:20:22 UTC
Permalink
In xenofarm, test_format seems to SEGV python interpreter.

test_fileinput
test_fnmatch
test_fork1
test_format
*** Termination signal 139 (ignored)
./python -E -tt ./Lib/test/regrtest.py -x test_pwd test_nis -x test_tempfile -x test_sunaudiodev test_grammar
testboth("%f", (1.0,), "1.000000")
'%f' % (1.0,) =? '1.000000' ... yes
zsh: segmentation fault ./python

Or, in condensed form :)

[ 23:16 ] - ./python
Python 2.3b1+ (#1, May 25 2003, 21:42:25)
[GCC 3.2] on hp-ux11
Type "help", "copyright", "credits" or "license" for more information.
formatstr = unicode("%f")
args = (1.0,)
result = formatstr % args
zsh: segmentation fault ./python

Unfortunately, -g is ignored by gcc on HP/UX, so I can't get a good
debug on this one:

(gdb) set args ../python/dist/src/Lib/test/regrtest.py test_format
(gdb) run
Starting program: /mp/slaskdisk/tmp/quest/build_python_taylor/python ../python/dist/src/Lib/test/regrtest.py test_format

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...test_format

Program received signal SIGSEGV, Segmentation fault.
0x77f870b8 in __fwrite_unlocked () from /usr/lib/libc.2
(gdb) bt
#0 0x77f870b8 in __fwrite_unlocked () from /usr/lib/libc.2
#1 0x77f873e8 in _doprnt () from /usr/lib/libc.2
#2 0x30303030 in ?? ()
Error accessing memory address 0x3030301c: Bad address.

Compiling the code using /opt/ansic/bin/cc passes the test. I say this
smells like gcc is a few horses short of a cavalry.
--
Anders "Quest" Qvist
http://www.lysator.liu.se/~sfarmer
Neal Norwitz
2003-05-25 23:51:06 UTC
Permalink
Post by Quest
In xenofarm, test_format seems to SEGV python interpreter.
Compiling the code using /opt/ansic/bin/cc passes the test. I say this
smells like gcc is a few horses short of a cavalry.
Yes, I don't have problems when testing with cc, only gcc. I think
the --without-gcc option should be passed to configure. I looked
briefly at adding the flag, but wasn't sure what to do in the sfarmer
acct.

Neal

Loading...