From: Jason Green To: Eli Zaretskii Cc: djgpp-workers AT delorie DOT com Subject: Re: Symify fixes Date: Mon, 28 Aug 2000 20:43:12 +0100 Message-ID: References: <226lqssqgqp6i9nk82rvrqhl9aaia029e9 AT 4ax DOT com> <7458-Mon28Aug2000203504+0300-eliz AT is DOT elta DOT co DOT il> In-Reply-To: <7458-Mon28Aug2000203504+0300-eliz@is.elta.co.il> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA32535 Reply-To: djgpp-workers AT delorie DOT com On Mon, 28 Aug 2000 20:35:05 +0200, you wrote: > > Can someone please tell me how do I build Symify (only) using the > > supplied makefiles. > > No makefiles required: 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. > > Also, if anyone has example sources to deliberately generate crash > > tracebacks I would be pleased to see it. > > This is impractical: I only see this once in a while with Emacs, which > is a 60MB source distribution. (Now, with the patched syms.c, I don't > see the crashes anymore ;-) When I did see that, copying the same > binary to another machine would usually prevent the crashes from > happening, since, as I now understand, random memory contents was > involved. Sorry, I should have been clearer. I want to generate some crash dumps to test symify with to see if anything is broken. This should not be difficult ;-) but I am open to suggestions for things to try. So far the following code is pretty successful in causing a crash :-) #include int main(void) { raise(SIGABRT); return 0; } To test the robustness of symify I was going to corrupt some .exe file. Again, I am open to suggestions on this. -- [please cc all replies, thanks]