Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!im4u!ut-sally!utah-cs!crum
From: crum@utah-cs.UUCP
Newsgroups: comp.sys.amiga
Subject: using (ram)wack 1.004 and other debuggers
Message-ID: <4223@utah-cs.UUCP>
Date: Wed, 28-Jan-87 15:13:54 EST
Article-I.D.: utah-cs.4223
Posted: Wed Jan 28 15:13:54 1987
Date-Received: Fri, 30-Jan-87 00:52:07 EST
Organization: University of Utah CS Dept
Lines: 62
Keywords: amiga symbolic debugging

[The following message is from Richard Carlson.  I will forward any replies
that I receive to him, in case your mail is unable to reach him.  I am also
interested in your experiences with MetaScope and sdb.  Of those debuggers,
which is most useful with the native Amiga development environment software?]

--------
   I have spent a lot of time tracking down programming errors in my C code
by using only Guru meditation numbers, and I would like to start using the
Wack debugger to speed up the debugging process.  Unfortunately, I cannot
even get Wack to correctly load any of my executable files.

   I am using Wack version 1.004 (the one which came with the 1.2 gamma 1
development system software), and I am running with 1.2 gamma 1 Kickstart
and Workbench.  Whenever I invoke Wack with the name of one of my programs,
Wack greets me with the following sequence:


Loading symbols..........................        [ or more or fewer dots ]
Unknown hunk type 4E56FFFC        [ or F0508F, or just about anything else ]

Could not load symbols
ready


   I have tried doing various things to solve this problem, including:
     - using either the version 3.02 or version 3.03 Lattice C compiler,
     - using or omitting the '-d' flag to LC1 (for line # information),
     - using or omitting the '-d' flag to LC2 (for symbol information),
     - linking with ALink version 2.30 or 2.32, or with BLink version 6.7,
     - linking my files in with AStartup.obj or LStartup.obj,
     - rearranging the order of my object module names for the linker, and
     - compiling and linking one big program rather than many modules.

   Every time I make a change in my method of compiling or linking, the
"unknown hunk type number" changes, but Wack consistently refuses to load
the executables.

   All of my programs run correctly, so it seems as though the executable
files themselves are not at fault (or at least that they are not missing
something essential).  Also, I have found that a previous version of Wack,
version 1.0, WILL correctly load the executables that confuse version 1.004
(although it seems that I previously had problems like this with version
1.0 as well).

   I have seen no previous mention of this problem on this newsgroup, so I
am obviously just doing something wrong.  If anyone can spot a possible
error in my technique, I would very much appreciate finding out what I
should be doing differently.

   Thanks in advance.

-- Richard

His address is currently:
arpa:	u-rlcarl@ug.utah.edu
uucp:	{decvax,ihnp4,seismo,ut-sally}!utah-cs!utah-ug!u-rlcarl

My (sender's) address is currently:
arpa:	crum@cs.utah.edu
uucp:	{decvax,ihnp4,seismo,ut-sally}!utah-cs!crum

[uucp hostnames utah-cs and utah-ug may change to cs.utah.edu and ug.utah.edu]