[jamming] Segfault w/ GCC 4.2

[Ryan Hill]

Building jam-2.5 with GCC 4.2 is causing a segfault when jam0 is run.

Compiling source in/var/tmp/portage/dev-util/jam-2.5-r3/work/jam-2.5 ...

cc -o ./jam0 -O2 -g -march=prescott -fomit-frame-pointer -fno-ident
-pipe builtins.c command.c compile.c execunix.c execvms.c expand.c
filent.c fileos2.c fileunix.c filevms.c glob.c hash.c headers.c jam.c
jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c
pathunix.c pathvms.c regexp.c rules.c scan.c search.c timestamp.c variable.c
execunix.c: In function 'execcmd':
execunix.c:235: warning: incompatible implicit declaration of built-in
function '_exit'
./jam0
make: *** [all] Segmentation fault

root at tycho ~/portage/dev-util/jam-2.5-r3/work/jam-2.5 # ./jam0
Segmentation fault
GNU gdb 6.6
Copyright (C) 2006 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 "i686-pc-linux-gnu".
(gdb) file jam0
Reading symbols from
/var/tmp/portage/dev-util/jam-2.5-r3/work/jam-2.5/jam0...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /var/tmp/portage/dev-util/jam-2.5-r3/work/jam-2.5/jam0

Program received signal SIGSEGV, Segmentation fault.
0x0804bf3d in hashitem (hp=0x805f2e0, data=0xbffb2588, enter=1) at
hash.c:108
108 keyval = *b;
(gdb) bt
#0 0x0804bf3d in hashitem (hp=0x805f2e0, data=0xbffb2588, enter=1) at
hash.c:108
#1 0x0804f279 in newstr (string=0x50891424 <Address 0x50891424 out of
bounds>) at newstr.c:52
#2 0x08050a41 in addsettings (head=0x0, setflag=0, symbol=0x50891424
<Address 0x50891424 out of bounds>, value=0x80a4168) at rules.c:253
#3 0x0804a08a in evaluate_rule (rulename=0x8060520 "Depends",
args=0xbffb2614, result=0x0) at compile.c:586
#4 0x0804a307 in compile_rule (parse=0x807cd80, args=0xbffb2684,
jmp=0xbffb26ac) at compile.c:518
#5 0x08049933 in compile_rules (parse=0x80a1490, args=0xbffb2684,
jmp=0xbffb26ac) at compile.c:630
#6 0x0804f59a in parse_file (f=0x8058150 "+") at parse.c:59
#7 0x0804c966 in main (argc=-1074056776, argv=0x0, arg_environ=0x3) at
jam.c:336

https://bugs.gentoo.org/show_bug.cgi?id=173703

-- 
                                where to now? if i had to guess
dirtyepic gentoo org        i'm afraid to say antarctica's next
9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)