[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

151.0. "metascope debugger" by ANYWAY::BROWN (Doug Brown) Mon Nov 03 1986 10:32

    Well, I finally got tired of trying touse WACK for the debugging
    of my programs.  I trecked down to the local amiga dealer and found
    a debugger that s more visually oriented; Metatscope.  It promised
    to be a real helpfull tool.  It has windows to display the break
    points, the hunks, memory contents, disassembled memory contents,
    and is supposed to be symbolic.  It contains an expression parser
    as well.   Alas, it does not display the "C" source code (I've been
    spoiled by the vms debugger).  Eagerly running home I recompiled
    my program with tthe lattice compiler, ran the debugger and voila,
    no symbols for my program....
      After much scratching of my head and purusing of the various
    documentation I have not been able to get the debugger to show me
    the symbols (global only, I guess) within my program.
      Does any one know how to get the METASCOPE debugger to work with
    the lattice compiler? Please?
T.RTitleUserPersonal
Name
DateLines
151.1Use -d VINO::PRATTMon Nov 03 1986 11:557
    I believe you should use the -d option to lattice. I don't remember
    if you need to specify it to LC1 or LC2 but I do know that both
    passes will accept it.
    
    -- Mark
    
    
151.2solution foundANYWAY::BROWNDoug BrownTue Nov 04 1986 13:0213
    It seems that all -d does is to include line offset numbers in the
    object file for use by the object module disassembler.  The new
    version
    of lattice that is comming out is reported to output symbol information
    when you use the -d switch.                                 
      I found the solution.  There is a utility supplied with the metascope
    debugger that will extract the symbol definition records from the
    object file and put them back into the object file inaa form that
    alink will accept.  This handy dandy little utility wawsq documented
    in one sentence in the manual....
    
      db