🚀 go-pugleaf

     I assume you mean libraries of the the .library type, ie; run time
libraries such as diskfont.library.  I wrote a run time library (req.library,
contains file requester, colour requester etc.) and found that the easiest way
to debug it was to link it in with the test program.  This guarantees that I
can use any debugger (sdb, cpr, metascope) to debug it with full symbolic
information.  This also avoids the annoying problem that everyone gets bitten
by at least once of not purging the library from memory and therefore testing
the previous version.  Disadvantages?  Very few.  You do you have to recompile
or relink your test program before trying with the real library, but that's
about it.

.bruce.