#1401: t/library/pcre.t: Test #2 failing on MSWin32
---------------------+------------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: library | Version: 1.9.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: win32 |
---------------------+------------------------------------------------------
Comment(by fperrad):
Replying to [comment:16 ronaldws]:
> Replying to [comment:15 ronaldws]:
> > Replying to [comment:12 fperrad]:
> > > I obtain the following output :
> > > ...
> > > > gdb -args parrot.exe t/library/pcre_2.pir
> > > GNU gdb (GDB) 7.1
> > > (gdb) r
> > > ok 1
> > > ok 2
> > > ok 3
> > > not ok 4
> > > not ok 5
> > >
> > Still wondering how to debug this.
>
> I now have an idea on how to debug the problem. The "not ok 4"
indicates that the parrot pcre library match function called the pcre
library pcre_exec function which returned a negative value. The negative
value is likely to be an error code which we might be able to decipher.
The pcre.t.dbg_patch file alters the the test to print out the return code
when it fails.
>
> Mr. Perrad, please apply the pcre.t.dbg_patch patch on your system, run
"prove -v t\library\pcre.t" and post the output.
>
I obtain :
{{{
> prove -v t\library\pcre.t
t\library\pcre.t ..
1..2
ok 1 - libpcre loading
not ok 2 - soup to nuts
# Failed test 'soup to nuts'
# at t\library\pcre.t line 104.
# got: 'ok 1
# ok 2
# not ok 3
# ok value seems to be error code - value is: -2
# not ok 4
# not ok 5
# '
# expected: 'ok 1
# ok 2
# ok 3
# ok 4
# ok 5
# '
# Looks like you failed 1 test of 2.
}}}
> Thanks,
> Ron
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1401#comment:17>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
