This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi 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: how to run the testsuite


Sebastian Reitenbach wrote:
On Tuesday 16 December 2008 21:34:54 Andreas Tobler wrote:
Sebastian Reitenbach wrote:
commenting them out, only lead to different errors, Illegal instructions,
segmentation faults, ...
therefore I added printf statements after each check to find out, it is
the third one, in the try catch statement, failing.
Ouch, I was wrong, the first two CHECK's are ok (also CHECK 4 and 5). If
you comment them the whole test goes funny.

What I wanted to see is the third CHECK (and 6th CHECK) to be commented
out. Or in other words, as it seems, you should change the test case. Try
to do the same on unwindtest_ffi_call.cc. It smells to me like a generic eh
(exception handling) problem
There the same problem shows up. a printf after the second CHECK doesn't show up. Commenting out the second CHECK only, still aborts the check.
.

Could you apply the patch below and tell me about the result from the log file?


To shorten the testsuite run do it this way:

make RUNTESTFLAGS='special.exp' check

Thanks,
Andreas

Index: unwindtest_ffi_call.cc
===================================================================
--- unwindtest_ffi_call.cc	(revision 142502)
+++ unwindtest_ffi_call.cc	(working copy)
@@ -44,7 +44,8 @@
 	ffi_call(&cif, FFI_FN(checking), &rint, values);
       } catch (int exception_code)
       {
-	CHECK(exception_code == 9);
+	//CHECK(exception_code == 9);
+	printf("ex code %d\n", exception_code);
       }
     printf("part one OK\n");
     /* { dg-output "part one OK" } */


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