Path: utzoo!mnetor!uunet!portal!cup.portal.com!DMasterson
From: DMasterson@cup.portal.com
Newsgroups: comp.sys.amiga
Subject: Re: MANX C & SDB
Message-ID: <3566@cup.portal.com>
Date: 29 Feb 88 05:04:12 GMT
References: <6823@oberon.USC.EDU> <649@applix.UUCP> <4036@husc6.harvard.edu> <8235@eleazar.Dartmouth.EDU> <7204@cisunx.UUCP>
Organization: The Portal System (TM)
Lines: 30
XPortal-User-Id: 1.1001.2888


In message (7204@cisunx.UUCP) ejkst@cisunx.UUCP (Eric J Kennedy) writes:
>In article <8235@eleazar.Dartmouth.EDU>, obie@eleazar.Dartmouth.EDU writes:
>> By the way, I HAVE received the Manx Source Level Debugger.
>> 
>> It is truly amazing, and a very useful programming tool.  It does what you 
>>would
>> expect it to, single-stepping through the program, setting breakpoints,
>> disassembling and viewing memory.  By the way, if you are thinking of 
>>learning
>> 68000 (10) assembly, the SDB is well worth the $75 purchase price for that
>> feature alone! When it disassembles your running code, it displays the C
>> statement, and then beneath it the Assembly code.
>
>Thanks for the good review!  One question, just how useful is SDB for
>someone who _doesn't_ know Assembly, and is not ready to take the plunge
>and learn it?  I know that DB is about useless to me.  Is SDB better?
>Okay, it has to be better if it's a source level debugger, but, really,
>will I get much out of it if I don't know the first thing about Assembly
>and don't particularly want to learn (yet) ?
>
It seems quite good to me.  The ability to step through source in its own
window makes debugging C programs quite fun.  The only problem I have right
now is trying to debug what's going wrong within one of the provided C 
functions (fgets()) when it tries to AllocMem.  I had to revert to assembly
to figure that much out.  The problem (I think) is that the debug files for
the libraries are not provided.

>------------
>Eric Kennedy
>ejkst@cisunx.UUCP