Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!cbosgd!ucbvax!apollo
From: jnp@BROWN.CSNET (Joe Pato)
Newsgroups: mod.computers.apollo
Subject: Re: /bin/cc, /com/cc, uupath, pathalias...
Message-ID: <8601291528.AA13445@mailhost.CS.Brown.CSNet>
Date: Wed, 29-Jan-86 10:28:25 EST
Article-I.D.: mailhost.8601291528.AA13445
Posted: Wed Jan 29 10:28:25 1986
Date-Received: Fri, 31-Jan-86 01:56:56 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28
Approved: apollo@yale-comix.arpa

>>	 The biggest problem is after running 'make' on the pathalias code
>>(it compiled fine) and running it on the uumap directory, I get a "Bus error"

>Try running the same program under the /com/sh.  You'll get a real error
>message.  Then type "tb".  You'll get a full stack trace back.  If that
>doesn't help, compile it with -g and use debug...

You don't have to run /com/sh in order to get a traceback.  The bourne
shell (/bin/sh) runs "inprocess" like the /com/sh and will allow you
examine the stack trace back.  If you run the Cshell (/bin/csh) you have
to set the "inprocess" shell variable in order to have the trace back
facility available.

If you don't normally run the Cshell "inprocess" you can still examine
process fault information by using /systest/ssr_util/fmpd. (fmpd will
format the process dump information stored in /sys/node_data/proc_dump.
It presents output that is a combination of /com/tb and /com/fst -a.)
Fmpd is normally used with the "-l" option which only displays information
for the last process dump, otherwise it will output information for all
dump records in the proc_dump file.


- Joe Pato
  Box 1910 - Dept. of Computer Science
  Brown University
  Providence, R.I. 02912 (USA)

  ARPA: jnp%brown@csnet-relay	UUCP: {decvax,ihnp4,allegra}!brunix!jnp