Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!mit-amt!atrp.media.mit.edu!ralph
From: ralph@atrp.media.mit.edu (Ralph L. Vinciguerra)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Debugging libraries with SDB.
Summary: What about debugging Workbench startup programs ?
Message-ID: <3640@mit-amt>
Date: 15 Mar 89 22:46:41 GMT
References: <10964@well.UUCP>
Sender: usenet@mit-amt
Reply-To: ralph@atrp.media.mit.edu (Ralph L. Vinciguerra)
Organization: MIT Amiga Users Group c/o MIT Cognitive Info. Processing Group
Lines: 11

In article <10964@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes:
>Since I asked this question a few months ago and got no response, I assume
>that people don't know.  It turns out that you *can* debug libraries with
>SDB.  SDB can maintain two sets of symbol and source code information, and
>if a ".dbg" file is created for the library, SDB can trace library calls
>in source mode.

Cana similar thing be done so that I can use SDB on workbench compatible
programs ? The old db had no problems, but SDB seems to insist on a
CLI startup. Ideas anyone (besides writing a front end to the program
which turns the CLI startup into a WB startup) ?