This is the mail archive of the java@gcc.gnu.org mailing list for the Java 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]

Re: no stacktrace available

From: Bart Locanthi <bart at sabl dot com>
To: tromey at redhat dot com
Cc: Andrew Haley <aph at redhat dot com>, "Boehm, Hans" <hans dot boehm at hp dot com>,Michael Koch <konqueror at gmx dot de>, java at gcc dot gnu dot org
Date: Wed, 15 Dec 2004 22:11:32 -0800
Subject: Re: no stacktrace available
References: <65953E8166311641A685BDF71D865826058BC3@cacexc12.americas.cpqcorp.net> <16832.5836.754594.663117@cuddles.cambridge.redhat.com> <m3sm675up2.fsf@localhost.localdomain>

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

References:
- RE: no stacktrace available
  - From: Boehm, Hans
- RE: no stacktrace available
  - From: Andrew Haley
- Re: no stacktrace available
  - From: Tom Tromey

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