A83: Re: gsinput

To: <assembly-83@lists.ticalc.org>
Subject: A83: Re: gsinput
From: "David Phillips" <electrum@tfs.net>
Date: Thu, 29 Oct 1998 23:07:20 -0600
Delivered-To: assembly-83-outgoing@towerguard.unix.edu.sollentuna.se
Reply-To: assembly-83@lists.ticalc.org


Try pushing/poping all the registers before you call the routine.  If it
doesn't crash, then you know that's where you problem lies.  Then you can
remove the push/pop pairs until you figure out which register is causing the
crash.  But getkey shouldn't ever crash unless you screw up memory
somewhere.  The only way you could make _vputs crash is to have bogus coords
set or pass it a bad pointer.  But it should just print giberish until it
finds a zero-byte.

-----Original Message-----
From: Chris Hiszpanski <mecad@scv.net>
To: assembly digest <assembly-83-digest@lists.ticalc.org>
Date: Thursday, October 29, 1998 11:03 PM
Subject: A83: gsinput


>
>I'm having a problem with Linus' numeric input. I read James' tutorial and
>followed the steps. Everything works but after I call the gsinput routine
>and return back to the place it was called from, I again _vputs a couple
>lines and call getkey. The calculator locks up and crashes. I think it has
>something to do with the gsinput messing up hl or some other register.
>
>From: Chris
>mecad@scv.net

Prev: A83: gsinput
Next: A83: Re: gsinput
Index(es):
- Main
- Thread