no stacktrace available

Thu Dec 16 06:10:00 GMT 2004

that would only work if there was a test that beat on gc in the presence 
of threads.
Tom Tromey wrote:
>>>>>>"Andrew" == Andrew Haley <aph@redhat.com> writes:
>>>>>>>>>>>>>>Andrew> The libgcj tests are designed to test, as far as possible, just one
>Andrew> thing like division, array access, and so on. Maybe we should also
>Andrew> have a smoke test for the gc.
>>For some reason we don't seem to regularly run "make check" in the GC
>build directory. Seems like that would work for this.
>>Tom
>>