Xref: utzoo alt.sys.sun:2552 comp.unix.questions:28218 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!pikes!csn!cs.colorado.edu!nieusma From: nieusma@cs.colorado.edu (Jeff Nieusma) Newsgroups: alt.sys.sun,comp.unix.questions Subject: Re: BAD TRAP Keywords: adb trace back Message-ID: <1991Jan24.203228.19169@csn.org> Date: 24 Jan 91 20:32:28 GMT References: <1991Jan23.002124.15503@ssd.kodak.com> Sender: news@csn.org (news) Reply-To: nieusma@cs.colorado.edu (Jeff Nieusma) Distribution: na Organization: CS Dept. University of Colorado, Boulder Lines: 38 Nntp-Posting-Host: cs.colorado.edu In article <1991Jan23.002124.15503@ssd.kodak.com>, dcox@ssd.kodak.com (Don Cox) writes: |> System: Sun4/260, SunOS4.0.3 |> |> Our news server (coop) has re-booted twice in the last week because |> of |> a "BAD TRAP". Below is a record of the /var/adm/messages file. Any |> ideas or suggestions as to what could be causing this would be |> greatly |> appreciated. Thanks. |> |> [ /var/adm/messages deleted ] |> |> Don Cox |> Phone (716) 253-7121 KMX (716) 253-7998 |> INTERNET dcox@ssd.kodak.com you should set your machine up to do a savecore when it crashes. after you get the core file, cd /var/crash/`hostname` adb -k vmunix.0 vmcore.0 $c $q The $c should show you a traceback complete with the names of the routines that were being executed when the crash occurred. It may help you determine what your problem is. +-----------------------------------------------------------------------------+ | Jeff Nieusma Logical: nieusma@cs.colorado.edu | | System Administrator/Programmer Audible: (303) 492-0677 | | Computer Science Department Physical: Campus Box 430 | | University of Colorado Boulder, CO 80309-0430 | +-----------------------------------------------------------------------------+ | I only work so I can afford to ski | +-----------------------------------------------------------------------------+