Path: utzoo!attcan!uunet!tronsbox!dfrancis
From: dfrancis@tronsbox.xei.com (Dennis Francis Heffernan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Assembly question from turnip
Keywords: can allocmem crash?
Message-ID: <272a5374-a00.6comp.sys.amiga.tech-1@tronsbox.xei.com>
Date: 28 Oct 90 06:00:45 GMT
References: <2728cc8d-a00comp.sys.amiga.tech@tronsbox.xei.com> <1990Oct28.12234
Lines: 27


	OK, I *knew* it had to be something stupid.  In all the sample code
I looked at, I somehow never noticed that it was a dollar sign in front of
the four and not a number sign.
	It hath been expunged.  I had already knocked out the byte references
in favor of longwords or moveq instructions.

	As for checking the condition codes, I was under the impression that
any time you moved a zero into a data register, the zero flag was set.  I 
don't see then how the system calls could NOT set the flag, but I'll take your
words for it.

	NEW QUESTION:  When you do an AllocMem(), do you get a pointer to the
TOP of the allocated area or the BOTTOM?  I'd think it'd be the top, but
after that first mistake...  (You want a better one?  Try this:
	jsr _LVOClose
	No problem, right...?  ;-)  Thankfully, I caught this one with Timo
Rossi's debugger/monitor, Mon- and thanks for the mail, Timo!  I had already
found Mon on a local board.  Of course, the sucker still crashes, but in a 
different spot now...)


dfrancis@tronsbox.xei.com   ...uunet!tronsbox!dfrancis     GEnie: D.HEFFERNAN1
"...when Fortran was introduced, it was claimed that Fortran would largely
eliminate coding and debugging!  Of course, that claim proved to be quite false"
- UNIVERSAL ASSEMBLY LANGUAGE, Robert M. Fitz & Larry Crocket