From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7aab61a1a53035c9
X-Google-Attributes: gid103376,public
From: kenner@lab.ultra.nyu.edu (Richard Kenner)
Subject: Re: Plea for help
Date: 1997/01/27
Message-ID: <5ci54b$om7$1@news.nyu.edu>#1/1
X-Deja-AN: 212509146
references: <9701231552.AA07941@most> <m2ybdgvyfz.fsf@acm.org>
organization: New York University Ultracomputer Research Lab
newsgroups: comp.lang.ada
Date: 1997-01-27T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <m2ybdgvyfz.fsf@acm.org> Corey Minyard <minyard@acm.org> writes:
>This cannot directly be done by user code on the SPARC.  To do a
>RELIABLE stack traceback on the SPARC requires interrupts to be turned
>off.  It can be done without it, but it will occasionally crash.  I
>wrote one of these for VxWorks on SPARC, but I could not use it on
>Solaris because it would occasionally crash.  Perhaps there is a
>system call to do it, but that would be the only way.

There is indeed a system call that dumps all register window information
into memory.