Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mailrus!ames!pasteur!ucbvax!STONY-BROOK.SCRC.SYMBOLICS.COM!jrd From: jrd@STONY-BROOK.SCRC.SYMBOLICS.COM (John R. Dunning) Newsgroups: comp.sys.atari.st Subject: Gulam problem Message-ID: <19880710165749.2.JRD@MOA.SCRC.Symbolics.COM> Date: 10 Jul 88 16:57:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 20 I'm in the throes of porting GNU Make, and have run into what looks like some kind of problem with gulam. The symptom is: when Make decides it needs to execute a command, it formats up the command name and arglist, and hands them off to a CLI. My CLI-finding routine does the obligatory lookup thru #x4F6, and jsr's to the resultant address, gulam's command executing routine in this case. The command gets executed perfectly, but when gulam returns to me, large tracts of memory have been trashed, including my stack. As you might imagine, things deteriorate in rapid fashion after that. Commenting out the actual JSR to gulam prevents the lossage. Pexec'ing the image directly causes no trouble. It happens repeatably (same garbage at same address) if I execute it a bunch of times. The same sort of thing (different values) happens with gulam 1.00.00.02 and 1.03.04.05. I'm not sure exactly what range of addresses are getting trashed, but it's at least in the range of a K or so, as I've dumped that much stack before and after the call, and seen it trashed. Anyone out there ever seen anything like this, or have any idea how to go about tracking down exactly what's happening?