On 21/07/06, chromatic <[EMAIL PROTECTED]> wrote:
On Thursday 20 July 2006 16:57, Fergal Daly wrote:

> On 21/07/06, chromatic <[EMAIL PROTECTED]> wrote:

> > Test an XS component.  Segfaults don't call done_testing_now().
> >
> > Yes, that happened to me last night.  Yes, I had 'no_plan' active.  Yes,
> > I noticed it as a happy accident, thinking "That test number looks
> > awfully low."
>
> My first thought was also XS and segfaults. Then I tried it
>
> $ perl -le 'print system("./segfault")'
> 11
>
>
> Test::Harness should pick this up. If the exit code is not a multiple
> of 256 then the program didn't exit normally,

Besides that, I realized that the harness ought to pick up the missing header
(which should occur at the end, with 'no_plan'), so it's not a good example.

But it sounds like there's a bug in the harness...

F

Reply via email to