Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!kuhub.cc.ukans.edu!markv
From: MARKV@kuhub.cc.ukans.edu (MARK GOODERUM - UNIV. OF KANSAS ACS - MARKV@UKANVAX)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Can one use CodeProbe to debug libraries?
Message-ID: <20967@kuhub.cc.ukans.edu>
Date: 9 Jan 90 15:41:47 GMT
References: <22138@usc.edu>
Organization: University of Kansas Academic Computing Services
Lines: 27

> I've been trying to find out from the Lattice manuals if the above (see 
> Subject:) is possible, and the documentation doesn't seem to either give 
> a yes/no answer or explain how to do it, if indeed this is possible (which 
> it is with MANX 3.6, though with a lot of juggling).  Has anybody tried this?

There is a command in cpr to enable tracing of calls into resident libraries.
I think you can also force it to look in the .library file for symbol tables
(assuming its your library) like you can with an executable file.  Otherwise
you just get assembler.

Lattice also says in their manual that debugging system resisdent libraries
can be dangerous in some cases (they don't say which cases).  Unfortunately
I am at work and cant give you the exact command.

My Lattice is 5.04 with the manual revisions, so if you cant find it I will
look for you.

> -- Marco Papa 'Doc'

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Gooderum			Only...		\   What to say, what to say..
Academic Computing Services	       ///	  \___________________________
University of Kansas		     ///  /|         __    _
Bix:	  gooderum	      \ \  ///  /__| |\/| | | _   /_\  makes it
Bitnet:   MARKV@UKANVAX		\/\/  /    | |  | | |__| /   \ possible...
Internet: mark@kuhub.cc.ukans.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~