Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!cbmvax!peter From: peter@cbmvax.commodore.com (Peter Cherna) Newsgroups: comp.sys.amiga.programmer Subject: Re: What does "trashing low memory vectors" mean? Keywords: CED, GOMF, vectors. Message-ID: <17303@cbmvax.commodore.com> Date: 9 Jan 91 20:48:40 GMT References: Reply-To: peter@cbmvax.commodore.com (Peter Cherna) Organization: Commodore, West Chester, PA Lines: 32 In article yorkw@stable.ecn.purdue.edu (Willis F York) writes: >Well just for the FUN of it i turned on GOMF's Lowmemory vector checking. >(DW was complaing about these vectors to, as wellas a nother anti-virus prog) > >and it seems EVERY time CED opens a File requestor, a Vector gets "trashed" > >the vector is 00000078, and it gets a value of 00c6f018, >What does this mean? What's a Low-memory-vector? There are areas of memory that some errant programs can damage, and they're in low-memory. GOMF watches for people who do this, and then restores the old contents, protecting those areas of memory. Now GOMF wedges into the OpenWindow() call for its own purposes, but it doesn't handle the failure of OpenWindow() correctly. CygnusEd tries to open a really big file requester, then successively smaller ones until it fits. Thus, OpenWindow() for the file requester can fail on account of the window being too big. The bug in GOMF causes low memory to be trashed, which GOMF then "discovers", and figures is CED's fault, when it's its own. > >C-ya.. > >-- >yorkw@ecn.purdue.edu Willis F York Peter -- Peter Cherna, Software Engineer, Commodore-Amiga, Inc. {uunet|rutgers}!cbmvax!peter peter@cbmvax.commodore.com My opinions do not necessarily represent the opinions of my employer. "Oh, PIN-compatible! I thought you wanted me to make it IN-compatible!"