Hello,

I'm encountering systems where repeated program runs yield different 
results (PIE and the like).  This means that the bigcore.exp (other 
tests as well?) technique of:

- run program, dump core
- debug program, capture state
- debug core, compare state

doesn't work - the corefile and debug inferior being separate program 
runs can yeild different results.  The attached changes bigcore.exp so 
that it causes the running inferior to dump core (instead of creating a 
new process) so that the results are identical:

- debug program, capture state
- core dump inferior
- debug core, compare state

It now also prints UNTESTED for any case where the test is aborted.  It 
was printing either warning or xfail :-/

Is this ok?  I just wonder if it should be generalized and moved to 
gdb.exp, I guess that should be a separate pass.

Tested on an amd64 GNU/Linux system.

Andrew