Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!mordor!styx!ames!ucbcad!ucbvax!sdcsvax!darrell
From: darrell@sdcsvax.UUCP
Newsgroups: mod.os
Subject: symbolic debugging
Message-ID: <2848@sdcsvax.UCSD.EDU>
Date: Tue, 10-Mar-87 23:20:38 EST
Article-I.D.: sdcsvax.2848
Posted: Tue Mar 10 23:20:38 1987
Date-Received: Fri, 13-Mar-87 00:13:45 EST
Sender: darrell@sdcsvax.UCSD.EDU
Organization: University of Minnesota
Lines: 18
Approved: mod-os@sdcsvax.uucp

In a recent posting, Kurt Vandenebrg (vanden@srcsip.uucp) asked an
interesting question in a somewhat non-specific way. Since this is
of interest to me either, I'll ask again:

Looking for leads on symbolically debugging compiled AND OPTIMIZED
code. The farther the distance between the high-level and compiled
code, the harder this is going to be. The toughest thing would
probably be from a high-level language directly to microcode (with
optimization!).

I think that LMI can compile (a subset of) zetalisp to microcode.
Can you instruct the compiler to optimize as well? Can you symbolically
debug the resulting program?

Are you developing/using/aware of other such systems?

Neta Amit (amit@umn-cs.arpa)
University of Minnesota CSci