Re: Segfault on Win32, the

2003-12-08 Thread Vladimir Lipsky
From: "Leopold Toetsch" <[EMAIL PROTECTED]> > Did you recheck that after my fix to vtable freeing? My patch covered > encoding and chartype too. No, I didn't. Did you fix the Parrot_loadbc function name? If didn't, I'll have a go for Parrot_set_PackFile() > leo 0x4C56 Happy .~.

Re: Segfault on Win32, the

2003-12-08 Thread Leopold Toetsch
Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > Some time ago I mentioned I'd been gettin' one more segfault while the > Parrot debug mode was on. In fact, it proved to be an effect of the > same cause -- we have global resources sharable among interpreters, > that we try to free more than once. This

Re: Segfault on Win32, the

2003-12-07 Thread Vladimir Lipsky
Some time ago I mentioned I'd been gettin' one more segfault while the Parrot debug mode was on. In fact, it proved to be an effect of the same cause -- we have global resources sharable among interpreters, that we try to free more than once. This time it's encoding_array. If you're going to disabl

Re: Segfault on Win32, The

2003-12-03 Thread Leopold Toetsch
Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > From: "Leopold Toetsch" <[EMAIL PROTECTED]> > Sent: Wednesday, December 03, 2003 12:05 PM >> The bug is already fixed. But we have to separate interpreter globals >> and real globals finally. Some time ago, I suggested to change the init >> functions sl

Re: Segfault on Win32, The

2003-12-03 Thread Vladimir Lipsky
From: "Dan Sugalski" <[EMAIL PROTECTED]> Sent: Tuesday, December 02, 2003 5:27 PM > Well, bah. I'll disable the table freeing for now and that should > take care of the bug at the moment, though it certainly won't cure > the underlying memory leak. > > Arguably, and this is getting into the rea

Re: Segfault on Win32, The

2003-12-03 Thread Vladimir Lipsky
From: "Leopold Toetsch" <[EMAIL PROTECTED]> Sent: Wednesday, December 03, 2003 12:05 PM > The bug is already fixed. But we have to separate interpreter globals > and real globals finally. Some time ago, I suggested to change the init > functions slightly to take a parent interpreter argument: Do

Re: Segfault on Win32, The

2003-12-03 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Well, bah. I'll disable the table freeing for now and that should > take care of the bug at the moment, though it certainly won't cure > the underlying memory leak. The bug is already fixed. But we have to separate interpreter globals and real globals fin

Re: Segfault on Win32, The

2003-12-02 Thread Dan Sugalski
At 1:52 AM +0300 12/2/03, Vladimir Lipsky wrote: I'm done with it for now and I'm not the dan to say which way is the parrot way to fix this bug Well, bah. I'll disable the table freeing for now and that should take care of the bug at the moment, though it certainly won't cure the underlying memo

Re: Segfault on Win32, The

2003-12-02 Thread Leopold Toetsch
Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > From: "Leopold Toetsch" <[EMAIL PROTECTED]> > Sent: Monday, December 01, 2003 5:47 PM >>Which child interpreter? Parrot_destroy_vtable() is called after >>free_unused_pobjects(). > Well you know test 61 in t/pmc/pmc.t causes a segfault. Its pmc_62 lab

Re: Segfault on Win32, The

2003-12-01 Thread Vladimir Lipsky
From: "Leopold Toetsch" <[EMAIL PROTECTED]> Sent: Monday, December 01, 2003 5:47 PM >Which child interpreter? Parrot_destroy_vtable() is called after >free_unused_pobjects(). Okay. I'll try to reword the problem all over again. Well you know test 61 in t/pmc/pmc.t causes a segfault. To get thing

Re: Segfault on Win32, The

2003-12-01 Thread Leopold Toetsch
Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > Umm .. the problem is that this pmc doesn't have the vtable; > (*((PMC *)b)).vtable points to a block of memory which belonged > to the child interpreter's pool and has already been freed, I deduce > from examining the adresses. So it ends up with Acces

Re: Segfault on Win32, The

2003-12-01 Thread Vladimir Lipsky
From: "Leopold Toetsch" <[EMAIL PROTECTED]> Sent: Thursday, November 27, 2003 12:04 PM > PMC (in gdb speak): > b dod.c:525 > r t/pmc/pmc_61.pasm > p *(PMC *) b > p *((PMC *) b)->vtable > c > ... Umm .. the problem is that this pmc doesn't have the vtable; (*((PMC *)b)).vtable points t

Re: Segfault on Win32, The

2003-11-27 Thread Leopold Toetsch
Vladimir Lipsky <[EMAIL PROTECTED]> wrote: > Well, currently, test 61 in t/pmc/pmc.t causes an abrupt stop of > the test session with the segfault box popping up. > if (PObj_active_destroy_TEST(b)) > VTABLE_destroy(interpreter, (PMC *)b); >

Segfault on Win32, The

2003-11-26 Thread Vladimir Lipsky
Well, currently, test 61 in t/pmc/pmc.t causes an abrupt stop of the test session with the segfault box popping up. I haven't yet taken a time to figure out what actually is the cause of trouble, but I've already detected the precise place where that all happens. It happens here void free_unused_