Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-08-03 Thread Leopold Toetsch
Am Donnerstag, 3. August 2006 22:27 schrieb Chip Salzenberg: > So, is the namespace iteration working now ... at least enough to close the > ticket that says "segfault" in large friendly lettes? The segfault in the first place wasn't related to namespaces at all, more to hash iteration abuse/bug/

Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-08-03 Thread Chip Salzenberg
So, is the namespace iteration working now ... at least enough to close the ticket that says "segfault" in large friendly lettes? -- Chip Salzenberg <[EMAIL PROTECTED]>

Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-07-17 Thread Leopold Toetsch
Am Montag, 17. Juli 2006 03:30 schrieb Bob Rogers: >    BTW, it doesn't seem right that I can run Parrot for only a second or > two and get more than 300K stack frames deep.  Isn't there a way to > limit the stack to something sane, since more than a few MB of C stack > usage is a pretty sure sign

Re: [perl #39778] Segfault when using a Namespace with an Iterator

2006-07-10 Thread Chip Salzenberg
On Sun, Jul 09, 2006 at 11:52:23PM -0700, Matt Diephouse wrote: > Trying to use an Iterator with a NameSpace makes Parrot segfault Ouch. The current namespace class is typed but in a silly way -- not with name mangling but with actually storing two things with exactly the same name. (One being a