Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!reed!psu-cs!smethers
From: smethers@psu-cs.UUCP (Paul Smethers)
Newsgroups: comp.sys.mac
Subject: Re: stack sniffer evils
Message-ID: <493@psu-cs.UUCP>
Date: 13 Feb 88 08:09:44 GMT
References: <363@moncsbruce.oz> <1142@iscuva.ISCS.COM>
Reply-To: smethers@psu-cs.UUCP (Paul Smethers)
Organization: SmethersBarnes
Lines: 19

In article <1142@iscuva.ISCS.COM> jimc@iscuva.ISCS.COM (Jim Cathey) writes:
>In article <363@moncsbruce.oz> conybear@moncsbruce.oz (Roland Conybeare) writes:
>>The solution:
>>	The ideal solution to this inappropriate bomb would be for Apple
>>to have provided some way of turning off the stack sniffer.  The next best
>>thing would be to do it ourselves.
>
>The stack sniffer is easily disabled by placing a zero in the global
>variable StkLowPt ($110-$113).  The sniffer code then ignores the
>stack.  When you're done, you should restore it to whatever it was so
>that the stack sniffer will start working again.  I don't remember
>where this was documented, but it is a relatively well-known technique.
>
I'm not sure if your new code is generated from a compiler or not, but if
you have control over it yourself (i.e. its your own assembler output), then
you may consider using a register other than A7 for your stack pointer.

Paul Smethers
SmethersBarnes