Date: Mon, 28 Aug 2000 23:47:27 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: mail AT jgreen4 DOT fsnet DOT co DOT uk Message-Id: <8011-Mon28Aug2000234727+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b CC: djgpp-workers AT delorie DOT com In-reply-to: (message from Jason Green on Mon, 28 Aug 2000 20:43:12 +0100) Subject: Re: Symify fixes References: <226lqssqgqp6i9nk82rvrqhl9aaia029e9 AT 4ax DOT com> <7458-Mon28Aug2000203504+0300-eliz AT is DOT elta DOT co DOT il> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Jason Green > Date: Mon, 28 Aug 2000 20:43:12 +0100 > > The reason I asked is that the supplied makefile has the lines: > > #relax error checking > XGCC=$(XLGCC) > > but the code will build with very extensive warnings turned on, so I > was thinking those lines could be removed. Looking again though, I > would say those lines could be for dbgcom.c, if that's so then they > should stay. Yes, this relaxation is for dbgcom.c. > I want to generate some crash dumps to test symify with to see if > anything is broken. Ctrl-BREAK is the usual way I do that. It's better than SIGABRT in that you can crash the program in different places by waiting different amounts of time before you press Ctrl-BREAK. > To test the robustness of symify I was going to corrupt some .exe > file. Again, I am open to suggestions on this. Write a program which inserts a 0xA0000 pointer dereference at random points of another program's source?