This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug driver/22600] Exit code should be different from 1 for internal compiler error


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-21 22:12 -------
I don't see why it should be different than 1.  It would only be helpful when you have automated builds 
but even then you need to look at the errors.

and for recursive crash testing you need to look for a pattern still as you might hit a different bug.
Here is a python script which I use as a wrapper:
#!/usr/bin/python
# Using delta debugging on GCC input
#import psyco
#from psyco.classes import *
import commands
import string
import sys

# Invoke GCC
(status, output) = commands.getstatusoutput("/Users/pinskia/local.c/libexec/gcc/powerpc-apple-
darwin7.9.0/4.1.0/cc1plus --param ggc-min-expand=0 --param ggc-min-heapsize=0 -quiet -O2 
-Wfatal-errors %s 2>&1" % sys.argv[1])

# Determine outcome
if status == 0:
  sys.exit(1)
elif string.find(output, "Segmentation Fault") >= 0:
  sys.exit(0)
else:
  sys.exit(1)


---- cut ----
You might want to look into delta for reducing testcases:
http://www.cs.berkeley.edu/~dsw/

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22600


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]