Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Joshua Gatcomb
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Joshua Gatcomb wrote: > > (gdb) p *pool > > $1 = {last_Arena = 0x1020, object_size = 32, > > objects_per_alloc = 16382, total_objects = 2048, > > num_free_objects = 2047, skip = 0, > replenish_level = > > 614, free_list = 0x1021, align_1 =

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Leopold Toetsch
Joshua Gatcomb wrote: (gdb) p *pool $1 = {last_Arena = 0x1020, object_size = 32, objects_per_alloc = 16382, total_objects = 2048, num_free_objects = 2047, skip = 0, replenish_level = 614, free_list = 0x1021, align_1 = 0, add_free_object = 0x4700f0 , get_free_object = 0x470110 ,

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Joshua Gatcomb
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Joshua Gatcomb wrote: > > I am not sure where to go from here. Any > suggestions? > > Ok, here is a sample debugging session: > > $ cat hello.pasm >print "hello\n" >end > > $ parrot hello.pasm > hello > > $ gdb parrot > ... > (gdb) b ne

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Joshua Gatcomb
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > #4 0x00423977 in enter_nci_method > (interpreter=0x100d1d68, type=26, func=0x481670, > name=0x53f8d9 "thread1", proto=0x53f8d4 > "vIOP") at > > Does the recent change related to NCI cure the > problem? > > leo Except for a few of the numbers

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Leopold Toetsch
Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x00419f6c in new_pmc_header (interpreter=0x100d1d68, > flags=1024) at src/headers.c:251 > 251 *((Dead_PObj*)pmc)->arena_dod_flag_ptr One more idea: When you set a breakpoint at C and (s

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Leopold Toetsch
Joshua Gatcomb wrote: I am not sure where to go from here. Any suggestions? Ok, here is a sample debugging session: $ cat hello.pasm print "hello\n" end $ parrot hello.pasm hello $ gdb parrot ... (gdb) b new_pmc_header (gdb) r hello.pasm Breakpoint 1, new_pmc_header (interpreter=0x82e5668, fla

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-07 Thread Leopold Toetsch
Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > #4 0x00423977 in enter_nci_method > (interpreter=0x100d1d68, type=26, func=0x481670, > name=0x53f8d9 "thread1", proto=0x53f8d4 "vIOP") at Does the recent change related to NCI cure the problem? leo

Re: Cygwin problems are GC not ICU

2004-05-06 Thread Joshua Gatcomb
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Somethings is *really* wrong here. I don't know > exactly what's happening > here, but I assume that the memalign function is > buggy. To nail that > further down: > > 1) Determine the used memalign function: > > $ grep memalign lib/Parrot/Config.p

Re: Cygwin problems are GC not ICU

2004-05-06 Thread Leopold Toetsch
Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > --- Leopold Toetsch <[EMAIL PROTECTED]> wrote: >> (gdb) bt >> (gdb) p pmc >> /gdb) p *((Dead_PObj*)pmc) >> would be good. > Program received signal SIGSEGV, Segmentation fault. > #5 0x0053fb75 in Parrot_ParrotInterpreter_class_init Early in program st

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-05 Thread Joshua Gatcomb
--- Leopold Toetsch <[EMAIL PROTECTED]> wrote: > (gdb) bt > (gdb) p pmc > /gdb) p *((Dead_PObj*)pmc) > would be good. Program received signal SIGSEGV, Segmentation fault. 0x00419f6c in new_pmc_header (interpreter=0x100d1d68, flags=1024) at src/headers.c:251 251 *((Dead_PObj*)pmc)->aren

Re: Cygwin problems are GC not ICU (was Re: Cygwin issues may not be ICU related)

2004-05-05 Thread Leopold Toetsch
Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x00419f6c in new_pmc_header (interpreter=0x100d1d48, > flags=1024) at src/headers.c:251 > 251 *((Dead_PObj*)pmc)->arena_dod_flag_ptr > |= (gdb) bt (gdb) p pmc /gdb) p *((Dead_PObj*)pm