Re: [Cppunit-devel] Signal handling in Linux

[Baptiste L. <gai...@fr...>]

----- Original Message -----
From: "Robert Wenner" <ro...@po...>
To: "Baptiste Lepilleur" <gai...@fr...>;
<cpp...@li...>
Sent: Tuesday, April 16, 2002 7:58 AM
Subject: Re: [Cppunit-devel] Signal handling in Linux


> Hi!
>
> On Monday 15 April 2002 23:44, Baptiste Lepilleur wrote:
> > So If I understood thing well, the only hope that remains would
> > compiler specific. VC++ has such a thing, have you found anything
> > like that on gcc ? (I guess not, but...)
>
> I think it would be compiler dependent, yes.
> I do not know the exact behaviour in VC++, but I did not even found
> something like a workaround on g++, as my C style stuff didn't work
> as expected I quickly dropped that topic and tried to have test cases
> that don't result in null pointer access -- not the bes solution, I
> know...

VC++ as a function called _set_se_translator() which allow you to set a
'translator' that is called to handle structured exception (the equivalent
of signal if I understood correctly) and convert them into C++ exception. In
any case, the stack frame is always unwinded correctly. Structured exception
are the equivalent for VC++ to a throw int(exception_type) (in debug mode),
which explains why catch(...) works for us even though we did not set any
exception translator.

>
> > In the meantime, I think I'll add a VerboseTestProgressListener:
> > startTest(): print test name
> > failure(): print ':' and 'E' or 'F'
> > endTest(): new line
> Better to be names BriefTestProgressListener?

Done. If you have others suggestions like that one, they are welcome. One of
the step that will be taken before going beta is renaming 'not so intention
revealing classes' (TestResult is a primary candidate but does not have its
final form yet).

Thanks,
Baptiste.