On Wed, May 22, 2002 at 12:34:22AM -0300, Daniel Grunblatt wrote: > On 22 May 2002, Sean O'Rourke (via RT) wrote: > > > # New Ticket Created by Sean O'Rourke > > # Please include the string: [netlabs #610] > > # in the subject line of all future correspondence about this issue. > > # <URL: http://bugs6.perl.org/rt2/Ticket/Display.html?id=610 > > > > > > > I believe there is a bug in how the perlhash pmc adjusts its buckets > > after reallocation. When the allocator hands it a new piece of > > memory that is aligned differently with respect to sizeof(HASHBUCKET) > > boundaries (32 bytes on linux-ppc), it will adjust pointers by a > > multiple of sizeof(HASHBUCKET), causing wierd segfaults. I believe > > the included patch fixes it. I didn't look for similar issues > > elsewhere, but the tests all seem to run now. > > > > Applied, thanks.
I apologize for the recent four-day tinderbox bonfire resulting from my tests 9 and 10 in perlhash.t. I should have been watching tinderbox more closely. It was one of those "works for me but hardly anyone else" bugs. (And of course, I got very busy on other things soon after committing them.) Which brings me to my question: is there some way of getting machine-readable output from tinderbox? I'd really like to alias my cvs commit to something that automatically monitors the tinderbox for the next hour and a half so it screams at me when I increase the current breakage level. But parsing the HTML looks like it would be difficult and fragile. Perhaps tinderbox already has something that I just don't know about? A simple event listing, in text or XML or whatever, would be perfect.
