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 (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

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

2004-05-05 Thread Joshua Gatcomb
--- Jeff Clites <[EMAIL PROTECTED]> wrote: > If you run it in a debugger (gdb or whatever), you > should be able to > see where it's crashing. Ok, after spending about 5 minutes figuring out what gdb was and how to use it (did I mention I was clueless) it looks like it isn't ICU at all Pro

Re: Cygwin issues may not be ICU related

2004-05-04 Thread Jeff Clites
On May 4, 2004, at 6:55 AM, Joshua Gatcomb wrote: Is it possible that parrot is coredumping for some other reason? The parrot.exe is around 3MB. I know that it isn't dying immediately upon execution because if the data file isn't in the directory it is supposed to be, invoking parrot.exe will com

Cygwin issues may not be ICU related

2004-05-04 Thread Joshua Gatcomb
All: While there are definately ICU issues on Cygwin, I have gotten it to link to parrot both statically and dynamically several different ways. The problem is that the resulting parrot.exe coredumps upon execution. I had always assumed that the problem was related to ICU since it was immediately