Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: 4.3BSD crash dump help needed
Message-ID: <15682@mimsy.UUCP>
Date: 28 Jan 89 07:14:49 GMT
References: <5483@bsu-cs.UUCP>
Distribution: usa
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 38

In article <5483@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>     _Xtransflt(800691d8,1) from 8000b5e7
>     _newproc(1) from _fork1+b3
>
>I have not found the Xtransflt symbol anywhere in the source or in any
>of the C libraries.  What am I overlooking?  The crash dumps always
>give a similar stack trace.  If only I could figure out what Xtransflt
>is I might have a clue.

Xtransflt is in locore.s.  The problem here is that adb is looking at
CALLG/CALLS stack frames, and a translation fault trap pushes a trap
frame instead, confusing it.  That Xtransflt() is almost certainly
procdup().  It may be related to this bug in resume():

RCS file: RCS/locore.s,v
retrieving revision 1.5
retrieving revision 1.6
diff -c2 -r1.5 -r1.6
*** /tmp/,RCSt1000249	Sat Jan 28 02:13:57 1989
--- /tmp/,RCSt2000249	Sat Jan 28 02:14:04 1989
***************
*** 1645,1650 ****
  1:
  	movl	r1,sp
! 	movl	(r0),(sp)			# address to return to
! 	movl	$PSL_PRVMOD,4(sp)		# ``cheating'' (jfr)
  	rei
  
--- 1645,1650 ----
  1:
  	movl	r1,sp
! 	pushl	$PSL_PRVMOD			# return psl
! 	pushl	(r0)				# address to return to
  	rei
  
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris