[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: clarify what else is nee

 Subject:   RE>clarify what else is needed
MCL will really get you much further than what you've experienced.
Double-click the frame-stack to get an inspector.  Use the pull-down
menu to indicate that you want to see the disassembly.  There will be
a marker at the current program counter (If you have always show
disassembly, then it will center on the marker when you inspect the
frame.  If not, one of the fields in the disassembly includes the PC,
scroll down to that address [look for the marker on the left].).  Look 
around the counter for function calls and symbol names
(ensure you compile with all the symbols options [see tool/environment].)
Match these with your source code (also using the thumb position as
an indication how deep in the code to look if you have long functions.)
It's not trivial, but it shouldn't take much to uniquely identify your
location in the code (not longer than 30 secs).

Date: 10/21/93 4:05 AM
To: Don Mitchell
Subject: clarify what else is needed

The problem is not finding your source code, but interpreting the backtrace
window in terms of your source code.  E.g., your code is running and get a
break - something ambiguous, like "NIL is not a structure."  What 
expression in your code was executing when this happened?  You open the
backtrace window with compiled code, and of course, all you see is which
lisp system function was executing; if your function has any length at all,
there will be many places where the same system function was called.  You
don't get any direct clues as to what piece of *your* code was executing -
that's because its compiled, of course.  ...

Donald H. Mitchell             Domain:  dhm@pro-solution.com
Proactive Solutions Inc.         UUCP:  uunet!proact!dhm   
5314 S. Yale Ave., Suite 402    Voice:  918.492.5192
Tulsa, OK  74135                  FAX:  918.492.5193