On Wed, Jun 29, 2005 at 08:37:44AM -0700, chromatic wrote:
> On Wed, 2005-06-29 at 10:59 -0400, Matt Fowles wrote:
>
> > Would it be reasonable to not run tests that are known to leave core
> > files? I feel like after a successful build there should not be
> > evidence like this left around...
>
On Wed, 2005-06-29 at 10:59 -0400, Matt Fowles wrote:
> Would it be reasonable to not run tests that are known to leave core
> files? I feel like after a successful build there should not be
> evidence like this left around...
People could set ulimit (though we'd have to tell them all to do that
Leo~
On 6/29/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Matt Fowles wrote:
>
> > Core was generated by `./parrot --gc-debug
> > /home/mfowles/perl6/parrot/t/pmc/io_1.pir'.
>
> Ah. ok. That's a TODO tests that is supposed to fail. It is testing io
> opcodes with undefs and integer PMCs.
>
On Wednesday 29 June 2005 15:24, Matt Fowles wrote:
> t/pmc/io_1.pir
Ah, yes. This is a failing todo test. The useage of IO ops on non IO-PMCs is
not specced yet.
jens
#6 0x08128193 in PIO_putps (interpreter=0x826e050, pmc=0x82a93e8,
s=0x843c7d8) at io/io.c:1011
1006INTVAL
1007PIO_put
Matt Fowles wrote:
Core was generated by `./parrot --gc-debug
/home/mfowles/perl6/parrot/t/pmc/io_1.pir'.
Ah. ok. That's a TODO tests that is supposed to fail. It is testing io
opcodes with undefs and integer PMCs.
As soon as the io opcodes are methods in ParrotIO we get type safety and
ap
Jens~
On 6/29/05, Jens Rieks <[EMAIL PROTECTED]> wrote:
> > #13 0x0808588e in main (argc=1, argv=0xb8ac) at imcc/main.c:637
> Can you please run
> print ((char**)0xb8ac)[1]
> to find out which file causes the coredump??
Sure!
> gdb ./parrot core
Core was generated by `./parrot --gc-debu
> #13 0x0808588e in main (argc=1, argv=0xb8ac) at imcc/main.c:637
Can you please run
print ((char**)0xb8ac)[1]
to find out which file causes the coredump??
jens
