Return to BSD News archive
Newsgroups: comp.os.386bsd.apps Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!library.ucla.edu!europa.eng.gtefsd.com!uunet!pipex!uknet!festival!castle.ed.ac.uk!richard From: richard@castle.ed.ac.uk (Richard Tobin) Subject: Re: Fvwm-0.97 X-Window System Window Manager available References: <NATION.93Sep21153316@snoopy.sanders.lockheed.com> <hastyCDqA3v.E23@netcom.com> <NATION.93Sep22075238@dopey.sanders.lockheed.com> Message-ID: <CDrCEo.8FC@festival.ed.ac.uk> Sender: news@festival.ed.ac.uk (remote news read deamon) Organization: University of Edinburgh Date: Wed, 22 Sep 1993 13:35:12 GMT Lines: 25 [I initially sent this by mail, but it bounced.] In article <NATION.93Sep22075238@dopey.sanders.lockheed.com> nation@dopey.sanders.lockheed.com (Robert Nation) writes: >- setitimer(ITIMER_REAL,value,NULL); >+ setitimer(ITIMER_REAL,&value,NULL); >For some reason SunOS4.1.3, and maybe all BSD systems tolerate the >error quite nicely, but SYSV type systems seem to have problems. It's a question of how the compiler passes structure arguments. Traditionally they were passed on the stack, so passing a structure instead of a pointer screws up. On Sparc machines, where arguments are normally passed in registers, structures are passed by making a copy and passing the address in a register. So it "just happens" to work. BSD vs SYSV shouldn't be an issue, except insofar as they use different compilers. -- Richard -- "For thousands of years, [homoeopathic magic] was known to the sorcerors of ancient India, Babylon and Egypt, as well as of Greece and Rome, and at this day it is still resorted to by cunning and malignant savages in Australia, Africa and Scotland." - J G Frazer, The Golden Bough