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=0.1 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,91c5b958fecf5eff X-Google-Attributes: gid103376,public From: Spam Hater Subject: Re: GNAT exception traceback Date: 1997/06/18 Message-ID: <33A85168.4E1A@no.such.com>#1/1 X-Deja-AN: 249424258 Sender: usenet@most.fw.hac.com (News Administration) X-Nntp-Posting-Host: sparc02 References: <199706131810.OAA07239@seahunt.ctron.com> <01bc7a82$c57186a0$2a208b82@wd> <33A6A725.3BD0@no.such.com> <33A6FAC5.9BB@no.such.com> Organization: See Warning Below! Newsgroups: comp.lang.ada Date: 1997-06-18T00:00:00+00:00 List-Id: > __builtin_frame_address() does not take variables (I played with it to > find this out :-). And, on the Sparc, having the frame address does > not give you the return address. Oh. Well, there you have it (or don't have it). > > Someone gave me SPARC assembler that allegedly works reliably > > when linked into a Verdix Ada program. I am not at liberty to > > release it, though, unless the originator reads this and says it's OK. > > I assume you mean a SPARC traceback facility :-). Yes, there is a > system call you can make under Solaris and SunOS to get this > information; that is what I would expect it would use. If on a > real-time platform, you can lock out interrupts and do the trace > yourself. I have code for both of these, but they are both extremely > slow. No system call or any other call. 40 lines of assembler, consisting of a little setup and a loopof nine instructions. The originator also claims it's fast. I didn't think to ask whether it is Verdix specific. > > With HPUX on PA RISC boxes, some C code I received from yet another > > kind soul has worked reliably for me when linked into Alsys programs. > > It may be that the Alsys compiler only uses one type of return > mechanism and it can be traced by reliably. I worked and worked and > finally asked HP; they told me (and pointed me to the place in the > manual with the information) about the difficulty when using their C > compiler. GCC seems to do the same thing. I should have said that I had also tested it in a _few_ C programs. Perhaps I should try more. > > Pentium with SCO Unix is one I haven't done, but would like to. > > Note that I am not claiming any expertise, just stating what has > > worked for me and others and making some wild guesses from that > > (in hopes that folks like Corey will keep on pointing out the bugs > > in the idea). > > SCO on Pentium should be easy, just the same as Linux on Pentium, the > original code you posted will work. Except that we may not always use gcc. (Plus they've decided to drop SCO and go to Windoze NT. Ugh!) -- ---------------------------------------------------------------------- Wes Groleau, Hughes Defense Communications, Fort Wayne, IN USA Senior Software Engineer - AFATDS Tool-smith Wanna-be Don't send advertisements to this domain unless asked! All disk space on fw.hac.com hosts belongs to either Hughes Defense Communications or the United States government. Using email to store YOUR advertising on them is trespassing! ----------------------------------------------------------------------