Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!purdue!haven!decuac!shlump.dec.com!michaud From: michaud@decvax.dec.com (Jeff Michaud) Newsgroups: comp.unix.ultrix Subject: Re: unaligned data access - Ultrix 3.0 (RISC) Keywords: DS3100 Ultrix 3.0 RISC Errors Message-ID: <3653@shlump.dec.com> Date: 20 Jul 89 23:10:48 GMT References: <2678@decuac.DEC.COM> <861@hadron.UUCP> Sender: news@shlump.dec.com Lines: 25 In article <2678@decuac.DEC.COM>, chris@winsrf.dec.com (Chris Cordrey) writes: > > "Fixed up unaligned data access for pid XXXXXXX (proc_name) at pc 0xNNNNNN" > see nac(1) for more info on how to shut off the messages. That should be uac(1). There is also a system call you can use to change it though I forget it's name at this time (it may be a syscall(2)). > (an obvious > performance hit which you can fix by aligning the offending variables > in your source - the trick is finding them!) Finding them is pretty easy. dbx the offending program, then dbx> 0xNNNNNN/10i will tell you the routine-name:linenumber of the offending source line. > VAXen are more forgiving in this area. Yes, but you take the performance hit in the microcode instead :-) -- /--------------------------------------------------------------\ |Jeff Michaud michaud@decwrl.dec.com michaud@decvax.dec.com| |DECnet-ULTRIX #include | \--------------------------------------------------------------/