Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Debugging libraries with SDB.
Message-ID: <15885@oberon.USC.EDU>
Date: 16 Mar 89 08:17:00 GMT
References: <10964@well.UUCP> <3640@mit-amt>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 25

In article <3640@mit-amt> ralph@atrp.media.mit.edu (Ralph L. Vinciguerra) writes:
>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.

Stuart, have you done it yourself?  I have tried with a "device" and
got nowhere. sdb always says that it cannot find the device, when I know
that mydev.dbg file is in the current dir and the device is loaded (after
the OpenDevice). Has anybody been able to do this REALLY?

>Can a 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) ?

Out of luck.  SDB does not handle workbench programs.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=