On Nov 29, 2007, at 10:13 PM, Patrick R. Michaud wrote:
Also, in case it matters, I'm on x86 (32-bit) for this.
Pm
Does it still occur after `ccache -C`? Since ccache uses md5, there's
always the possibility you inadvertently discovered a collision in md5.
Might want to back up ~/.ccac
On Thu, Nov 29, 2007 at 06:17:57PM -0800, chromatic wrote:
> On Thursday 29 November 2007 18:05:32 Patrick R.Michaud wrote:
>
> > Yes, that subject line is correct -- I've found a bug
> > that shows itself _only_
> >- when I build Parrot using ccache,
> >- for one seemingly obscure json te
On Thursday 29 November 2007 18:05:32 Patrick R.Michaud wrote:
> Yes, that subject line is correct -- I've found a bug
> that shows itself _only_
>- when I build Parrot using ccache,
>- for one seemingly obscure json test,
>- when running Parrot with the --gc-debug core (e.g., 'make te
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #47970]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47970 >
Yes, that subject line is correct -- I've found a bug
that shows itself _only_
