Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!rkb55989 From: rkb55989@uxa.cso.uiuc.edu (Rafal) Subject: Re: Gcc 2.3.3 bug ? Date: Tue, 6 Apr 1993 22:52:44 GMT Message-ID: <C533Jw.Cwu@news.cso.uiuc.edu> References: <1993Apr6.154454.22346@cm.cf.ac.uk> <1psj0a$40t@smurf.sub.org> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Organization: University of Illinois at Urbana Lines: 29 urlichs@smurf.sub.org (Matthias Urlichs) writes: >In comp.os.386bsd.bugs, article <1993Apr6.154454.22346@cm.cf.ac.uk>, > paul@isl.cf.ac.uk (Paul) writes: >> >> Dump of assembler code from 0x68 to 0x78: >> [...] >> >> I'll start looking into it but does anyone have any ideas, seems like >> it's probably a generic i386 problem with gcc-2.3.3. >It isn't -- under Linux the above code looks identical (OK, the addresses >are different) and it doesn't crash. I have also seen this sort of thing when compiling Seyon 1.8 and 2.06 [and every version I tried in between] under 386BSD... The same GCC2.3.3 output code causes a SIGSEGV on BSD but runs fine on Linux... If someone is going to look at this, please email me, and I'll post or send you the code in question.. >Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ >Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany -- +49-721-9612521 \o)/ /------------------------------------------------------------------------\ |Rafal Boni r-boni@uiuc.edu| |"Me have a .sig?? I don't even have a clue!" rkb55989@uxa.cso.uiuc.edu| | -Anonymous rb6775@caffeine.cen.uiuc.edu| \------------------------------------------------------------------------/