[perl #49836] [BUG] segfault in ascii_compare

2008-02-19 Thread Will Coleda via RT
On Mon Jan 21 19:05:10 2008, [EMAIL PROTECTED] wrote: On Sunday 20 January 2008 21:31:08 Will Coleda via RT wrote: Spent some more time trying to track this down. On OSX/86, I was able to reproduce the segfault with much less tcl code: %cat foo.tcl after 10 %./tclsh foo.tcl if I

Re: [perl #49836] [BUG] segfault in ascii_compare

2008-01-21 Thread chromatic
On Sunday 20 January 2008 21:31:08 Will Coleda via RT wrote: Spent some more time trying to track this down. On OSX/86, I was able to reproduce the segfault with much less tcl code: %cat foo.tcl after 10 %./tclsh foo.tcl if I ran: %../../parrot -G tcl.pbc foo.tcl The segfault goes

Re: [perl #49836] [BUG] segfault in ascii_compare

2008-01-20 Thread Will Coleda
On Jan 19, 2008 10:27 PM, chromatic [EMAIL PROTECTED] wrote: On Saturday 19 January 2008 19:20:22 Will Coleda via RT wrote: Original command line has a slight red herring: the duplicated file name is irrelevant: ./tclsh t/cmd_after.t causes the same issue. (chromatic++ fixing the

[perl #49836] [BUG] segfault in ascii_compare

2008-01-20 Thread Will Coleda via RT
On Sun Jan 20 13:17:03 2008, coke wrote: On Jan 19, 2008 10:27 PM, chromatic [EMAIL PROTECTED] wrote: On Saturday 19 January 2008 19:20:22 Will Coleda via RT wrote: Original command line has a slight red herring: the duplicated file name is irrelevant: ./tclsh t/cmd_after.t

[perl #49836] [BUG] segfault in ascii_compare

2008-01-20 Thread Will Coleda via RT
Spent some more time trying to track this down. On OSX/86, I was able to reproduce the segfault with much less tcl code: %cat foo.tcl after 10 %./tclsh foo.tcl if I ran: %../../parrot -G tcl.pbc foo.tcl The segfault goes away, which smells like a GC issue. However, I can't duplicate it with

[perl #49836] [BUG] segfault in ascii_compare

2008-01-19 Thread Will Coleda via RT
On Wed Jan 16 10:53:25 2008, coke wrote: On Jan 16, 2008 1:45 PM, chromatic via RT [EMAIL PROTECTED] wrote: On Wednesday 16 January 2008 07:03:02 Will Coleda wrote: Here's (a new, I think) segfault that partcl exposes (r24918) build tcl. %../../parrot tcl.pbc t/cmd_after.t

Re: [perl #49836] [BUG] segfault in ascii_compare

2008-01-19 Thread chromatic
On Saturday 19 January 2008 19:20:22 Will Coleda via RT wrote: Original command line has a slight red herring: the duplicated file name is irrelevant: ./tclsh t/cmd_after.t causes the same issue. (chromatic++ fixing the tclsh binary!) I can't reproduce it on x86 GNU/Linux. Did 24163

[perl #49836] [BUG] segfault in ascii_compare

2008-01-16 Thread via RT
binhn8te6Y4Jn.bin Description:

Re: [perl #49836] [BUG] segfault in ascii_compare

2008-01-16 Thread chromatic
On Wednesday 16 January 2008 07:03:02 Will Coleda wrote: Here's (a new, I think) segfault that partcl exposes (r24918) build tcl. %../../parrot tcl.pbc t/cmd_after.t t/cmd_after.t Segmentation fault FYI, this command line isn't expected to do anything useful at the moment; I'm only