Newsgroups: comp.sys.atari.st
Path: utzoo!utgpu!watserv1!watmath!ljdickey
From: ljdickey@watmath.waterloo.edu (L.J.Dickey)
Subject: szadb for gcc user
Organization: University of Waterloo
Date: Fri, 11 Jan 91 04:33:10 GMT
Message-ID: <1991Jan11.043310.27768@watmath.waterloo.edu>
Lines: 48

[ This message is from and on behalf of Michal Jaegermann.
Please respond to him at your appropriate variant of
one of these addresses:
 	NTOMCZAK at UALTAVM
 	NTOMCZAK%UALTAVM.bitnet@ugw.utcs.utoronto.ca
ljdickey ]

The recently posted szadb 1.2 debugger seems to have a slightly
different opinion than gcc about what constitutes a command line
and where to look for it.  To help to restore overall sanity I am
using a key definiton file similar to the following one.  If you
are gcc user you may try that to.

---------------------------/ cut here /------------------------------
#
# A sample adb key definion file for gcc compiled programs.
# Use as follows 'adb -k fixargs.adb <debugee> [remaining args...]'
#
F1  $k11; $k13 ; $k14; $k15; $b; :c; main:d
#
# <sp,10/x instructions in two following commands mostly
# for demonstration and reassurance purposes.
#
F11 main:b <sp,10/x; $k12
#
# Magic numbers 3 and c below refer to a number of pointers to
# arguments to skip, i.e 'adb -k fixargs.adb'.  Adjust as needed.
#
F12 <sp/W *(<sp+4)-3; <sp+4/W *(<sp+8)+c; <sp,10/x
#
# Replace by your desired breakpoints.  They do not have to be
# all defined - even if referenced in F1.
#
F13 getitime:b
F14 getctime:b
#F15 localtim:b
---------------------------/ cut here /------------------------------

To use that file start szadb with a command line like in a comment
above.  Of course you better have a symbol table.  When you will get
adb prompt hit F1 function key followed by <Return>.  Watch results.
The next <Return> will carry you to your first breakpoint (provided
you did not set it up ouside of an execution path :-)).

    Enjoy,
    Michal Jaegermann
    ntomczak@ualtavm.bitnet