Compilable C Curry Challenge!

C and C++ are both statically typed. And thus it seems like a fun challenge to write a program in C or C++ that writes source code by looking in header files for functions to call and then randomly mashes them together and passes the results to other functions.

I wonder how long it'd take before you'd find a kernel bug this way.

Has anyone ever done this?

>>4
Is that so bad, though? I don't think >>1 is suggesting that these programs be run on any system of importance (since the goal of finding a kernel bug would defeat the purpose of that), so a few segfaults or attempted invalid writes should be no problem. I would imagine the setup would be a virtualized machine that continually generates programs, communicates them to the host, then executes them, leaving the host to detect whether Something Bad happened.

I think the real problem would be non-terminating programs and user input. Who knows? Maybe sleeping for more than 49482 seconds is a kernel panic on the 49483^rd! That's something I'd like to know.