The goops failures are a side effect of a change I made to (initialize <generic> ...) so that adding a method to no-applicable-method wouldn't crash; the warning arises from the generic function having one method instead of none after define-generic is called.  There are details on bug-guile here:

http://lists.gnu.org/archive/html/bug-guile/2006-09/msg00002.html

It seems that char 254 doesn't behave as expected in regular expressions on this platform. 

I backed out the change to initialize <generic> and make check lists only the two failures for regexps with char 254, but the same steps still corrupt the heap.

thanks
pat


On 9/18/06, Pat Lasswell <imofftoseethewizard@gmail.com> wrote:
make check produces 6 failures.  I haven't tried 1.4, but 1.8 doesn't even build.

FAIL: goops.test: defining generics: define-generic: creating a new top-level binding
FAIL: goops.test: defining generics: define-generic: overwriting a top-level binding to a generic
FAIL: goops.test: defining accessors: define-accessor: creating a new top-level binding
FAIL: goops.test: defining accessors: define-accessor: overwriting a top-level binding to an accessor
ERROR: regexp.test: regexp-quote: regexp/extended: (char 254 ? ? ?) - arguments: ((regular-expression-syntax "make-regexp" "empty (sub)expression" #f #f))
FAIL: regexp.test: regexp-quote: regexp/extended: (string "aX" 254 ? a? a?)
FAIL: regexp.test: regexp-quote: regexp/extended: string of all chars



On 9/18/06, Ludovic Courtès <ludovic.courtes@laas.fr> wrote:
Hi,

"Pat Lasswell" <imofftoseethewizard@gmail.com> writes:

> In guile 1.6.8 on an intel mac, I've encountered reliable heap corruption with
> steps like the following

Before investigating any further, does Guile 1.6.8 "works" on Intel
Macs?  Is it under MacOS X?  For instance, did you successfully run the
test suite (type `make check' under the top-level source directory)?

Thanks,
Ludovic.