Path: utzoo!utgpu!jarvis.csri.toronto.edu!db.toronto.edu!fche
Newsgroups: comp.sys.amiga.tech
From: fche@db.toronto.edu (Frank Ch. Eigler)
Subject: Manx SDB (3.6) bug?
Message-ID: <1990Jan3.184409.4061@jarvis.csri.toronto.edu>
Summary: Trace and execution different!
Reply-To: fche@db.toronto.edu
Organization: University of Toronto, CSRI
Date: 3 Jan 90 23:44:09 GMT
Lines: 39


Hi, again, folks.

I haven't quite gotten to Manx 5.0 yet..  But just found a
seeming anomaly in SDB of 3.6a.

Singlestepping a program behaves differently than actually
running it.  Everything else is the same (ie. plenty of
memory, etc.), except it's not getting stopped after every line.

The problem seems to be around an AllocMem() call.  I invoke it
as:

#define SSIZE ((ULONG) sizeof(struct Big96ByteStruct))

	ptr = AllocMem(SSIZE, MEMF_PUBLIC | MEMF_CLEAR);

This AllocMem() just doesn't want to succeed while being single-
stepped.  SSIZE is confirmed at 96L.  There is 400K free.

When the program is run straight, it does succeed (but fail at
a different point ...  I don't know WHERE because SDB dies long
before then!).


This is strange.

Any suggestions?  (I will try using a variable instead of a macro
there, and see how it works out, but it _shouldn't_ make any
difference, should it?!)

Thanks! (again!)

--Frank
-- 
  Frank Ch. Eigler                                              //
    fche@db.toronto.edu                                        //
                                                           \\ //
"I'll be your sledgehammer"                           AMIGA \X/