lists.zerezo.com
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
***BOGO*** Re: [Mingw-users] GCC 4.3.0 20080502 (alpha) Released - Please help us test it!
- Date: Sun, 18 May 2008 19:31:08 -0600
- From: "Weddington, Eric" <eweddington@xxxxxxxxxxxxx>
- Subject: ***BOGO*** Re: [Mingw-users] GCC 4.3.0 20080502 (alpha) Released - Please help us test it!
> -----Original Message-----
> From: mingw-users-bounces@xxxxxxxxxxxxxxxxxxxxx
> [mailto:mingw-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf
> Of Ramiro Polla
> Sent: Saturday, May 17, 2008 6:14 AM
> To: mingw-users@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Mingw-users] GCC 4.3.0 20080502 (alpha)
> Released - Please help us test it!
>
> >The proper way to proceed on these kinds of bugs is to
> minimize the test
> > case, so you end up with the smallest possible run of code that
> > demonstrates the bug.
> >
> > The general process for runtime failures is to 1) try to
> all get all
> > relevant code into a single .c file that still demonstrates
> the problem,
> > 2) preprocess it with -E or -save-temps 3) remove all code
> you can while
> > retaining the bug and not causing other failures.
>
> I was hoping I wouldn't have to go this far, since as I mentioned the
> file is huge and it'd take me quite some time to create a minimal
> testcase. I'm also a GSoCer, so I won't have time to work on this...
> Sorry, but good luck on your project =)
>
The software package 'delta' was designed to automatically reduce test
cases:
<http://delta.tigris.org/>
Works wonders for me.
Eric Weddington
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users