Re: [perl #43219] segfault in tcl

On Thursday 14 June 2007 22:17:25 Mark Glines wrote: > I poked around a bit in gdb. I don't have any answers or patches, but > hopefully a little more information will be helpful. > > In Parrot_get_HLL_id, between the 31st and 32nd calls to this function, > the string memory for the "name" string

Re: [perl #43219] segfault in tcl

On Thu, 14 Jun 2007 19:10:02 -0700 Will Coleda (via RT) <[EMAIL PROTECTED]> wrote: > # New Ticket Created by Will Coleda > # Please include the string: [perl #43219] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=43219 >

[perl #43219] segfault in tcl

# New Ticket Created by Will Coleda # Please include the string: [perl #43219] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43219 > With recent updates, tcl suite is MUCH faster, but is now segfaulting in several places

Re: [perl #43218] Memory leaks (compreg, invokecc)

On Thursday 14 June 2007 14:42:31 Jurosz Michal wrote: > Attached test use compreg P1, "PASM" and invokecc it 100,000 times. > On win32 (mingw32) it consumes 70MB of RAM with r18834 (107 MB of RAM > with r11704). With Linux at r19010, the memory use jumped up to 62 MB for me. However, Valgrind s

[perl #43218] Memory leaks (compreg, invokecc)

# New Ticket Created by Jurosz Michal # Please include the string: [perl #43218] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43218 > Attached test use compreg P1, "PASM" and invokecc it 100,000 times. On win32 (mingw32)

Re: Last bits of PDD 15 implementation

Allison Randal wrote: I'm about half-way through a quick classification of the failing PDD 15 tests (in t/pdd15oo). A number of the failures are quick things anyone could pick off, so I'll share the list: We're only failing 157 ou

Re: [GC] Pin Key PMCs During Method Lookup

Am Mittwoch, 13. Juni 2007 05:02 schrieb chromatic: > PMC   * const key = VTABLE_nextkey_keyed(interp, key_new(interp), > ns, ITERATE_FROM_START); > > If a GC run happens in the rest of this function, it could collect the > newly created Key -- PMCs created and held outside of structures vi