done;
}
}
## .close;
}
});
In my particular case, the input from port 5000 is RAW IRC lines relayed
through a socket from a script running under my client; live input. The
above program terminates abnormally with the error message after a few
thousand lines:
*** E
As noted above the tests in S02-types/bool.t are passing for quite a while.
The only remaining problem was the segmentation fault with parrot when running
'(0 but Bool::True) and print qq{$_ } for 1..1000;'.
I just tested with the latest Rakudo Star (2015.02) and I was unable to
reproduce the s
Since the tests in S02-types/bool.t pass, the relevant problem seems to be the
for loop with "0 but Bool::True".
I don't see any crashes within the first 100 iterations, but on Parrot I get
segfaults or crashes with around 262 iterations. On Moar and JVM there are no
problems:
$ perl6-m -e '(0
# New Ticket Created by Ira Byerly
# Please include the string: [perl #116933]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org:443/rt3/Ticket/Display.html?id=116933 >
Script started on Mon 25 Feb 2013 08:40:18 PM HST
$
$
$
$ perl6 -v
This is perl6
chromatic wrote:
> In theory, this patch should apply and run cleanly. It doesn't.
>
> Thus, something somewhere pokes into memory it shouldn't.
>
> Any ideas? Alternately, any comments on this analysis?
I think adding memory checks is a brilliant idea, especially because
memory is sometimes r
On Thursday 05 July 2007 19:58:50 Patrick R. Michaud wrote:
> I also get segfaults after applying this patch.
>
> However, if I change the patch such that the "size_t sentinel;"
> line goes at the end of the struct PMC instead of the beginning,
> then everything appears to compile and run.
>
> In
On Thu, Jul 05, 2007 at 06:30:44PM -0700, chromatic wrote:
> In theory, this patch should apply and run cleanly. It doesn't.
>
> Thus, something somewhere pokes into memory it shouldn't.
>
> Any ideas? Alternately, any comments on this analysis?
I also get segfaults after applying this patch.
In theory, this patch should apply and run cleanly. It doesn't.
Thus, something somewhere pokes into memory it shouldn't.
Any ideas? Alternately, any comments on this analysis?
-- c
=== include/parrot/pobj.h
==
--- include/parrot
Steve Fink wrote:
Hey, your reason is much better than my reason. Still, why do the
_noinit stuff and duplicate the creation code? Why not just call pmc_new
as in my replacement code?
C would create a Hash already. But the clone has to create one
of the source type, which might not be quite the sa
On Sep-09, Leopold Toetsch wrote:
> Steve Fink (via RT) wrote:
>
> >I won't go through all the details of what I looked at (though I'll
> >post them in my blog eventually), but what's happening is that this
> >line (from perlhash.pmc's clone() implementation) is corrupting the
> >flags field:
> >
Steve Fink (via RT) wrote:
I won't go through all the details of what I looked at (though I'll
post them in my blog eventually), but what's happening is that this
line (from perlhash.pmc's clone() implementation) is corrupting the
flags field:
((Hash*)PMC_struct_val(dest))->container = dest
# New Ticket Created by Steve Fink
# Please include the string: [perl #31493]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31493 >
---
osname= linux
osvers= 2.4.21-1.1931.2.382.entsmp
arch= i386-linux-thread-multi
cc
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Steve Fink <[EMAIL PROTECTED]> wrote:
>> It crashes on a memcpy inside compact_pool
> Some remarks what I could find out:
> - current COW copying of stacks is AFAIK borken - both "copies" of
> one COWed stack share the same Buffer header
I have now
Steve Fink <[EMAIL PROTECTED]> wrote:
> Here's another obnoxious test case.
[ ... ]
> So, in case anyone is curious (hi leo!), attached is a 56KB (<9KB
> gzipped) imc file.
> It crashes on a memcpy inside compact_pool
Some remarks what I could find out:
- the damaged Buffer is in a pool of obje
Here's another obnoxious test case. I started to try to strip it down,
but it starts working again if I even delete nonsense lines from a
subroutine that is never called. And I'm working on something else and
not at all in the mood to re-learn how to debug parrot internals. It
turns out that I don'
On Nov-21, Leopold Toetsch wrote:
> Steve Fink <[EMAIL PROTECTED]> wrote:
> > I'm staring at a crash
>
> > I'll attach the 5KB compressed .imc file (25KB uncompressed; PIR code
>
> Its really good, to have such short code snippets, that clearly show,
> where a bug is coming from ;) Anyway, it was
Steve Fink <[EMAIL PROTECTED]> wrote:
> I'm staring at a crash
> I'll attach the 5KB compressed .imc file (25KB uncompressed; PIR code
Its really good, to have such short code snippets, that clearly show,
where a bug is coming from ;) Anyway, it was again me causing this bug -
sorry.
Fixed and u
I'm staring at a crash, my eyes are glazing over, and I need sleep. So
I was wondering if anyone would be interested in taking a look at a
.imc file that is giving me a seg fault while marking a hash in a gc
run triggered by a hash PMC allocation. Or at least tell me whether
it's seg faulting on yo
At 07:57 PM 3/29/2002 +0200, you wrote:
>"Michel J Lambert" <[EMAIL PROTECTED]> wrote:
>
> > Attached is a .pasm file which causes some string data to be written into
> > the middle of the string_pool->pool_buffer list of entries, such that when
> > it tries to dereference foo in new_pmc_header, i
"Michel J Lambert" <[EMAIL PROTECTED]> wrote:
> Attached is a .pasm file which causes some string data to be written into
> the middle of the string_pool->pool_buffer list of entries, such that when
> it tries to dereference foo in new_pmc_header, it's pointing to garbage
> memory. 0x20202020 for
I've been using clintp's pasm test script for much of my testing, which is
supposed to be an infix expression evaluator. I've been stress-testing
parrot and finding bugs by putting increasingly-large expressions into the
pasm file for it to evaluate.
Attached is a .pasm file which causes some str
21 matches
Mail list logo
