From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pat Lasswell" Newsgroups: gmane.lisp.guile.user Subject: Re: Need help finding heap corruption bug Date: Mon, 18 Sep 2006 08:08:31 -0700 Message-ID: References: <877j01pojo.fsf@laas.fr> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0565020632==" X-Trace: sea.gmane.org 1158592146 20847 80.91.229.2 (18 Sep 2006 15:09:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 18 Sep 2006 15:09:06 +0000 (UTC) Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Sep 18 17:09:05 2006 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GPKjs-0003bT-J4 for guile-user@m.gmane.org; Mon, 18 Sep 2006 17:08:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GPKjs-00056g-1Y for guile-user@m.gmane.org; Mon, 18 Sep 2006 11:08:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GPKjb-0004z8-TB for guile-user@gnu.org; Mon, 18 Sep 2006 11:08:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GPKjY-0004xo-Tn for guile-user@gnu.org; Mon, 18 Sep 2006 11:08:35 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GPKjY-0004xk-Ok for guile-user@gnu.org; Mon, 18 Sep 2006 11:08:32 -0400 Original-Received: from [64.233.166.178] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GPKmQ-0000JU-7C for guile-user@gnu.org; Mon, 18 Sep 2006 11:11:30 -0400 Original-Received: by py-out-1112.google.com with SMTP id d42so4230680pyd for ; Mon, 18 Sep 2006 08:08:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ocMvMBMIQz+OzasWdfcf83buCTfHyw9TWn0DSrWbhDCcd7aQGJSC3dArn3YJy1C7v6du5drzAJQl6gCAmlIv0c+jmkQXzWdQvfrpAloWEdRH3f6rtivGyupLMgzPD76myKiPtu1G4wERXLEHYP8BhUQQDkHEv/2kmJ72fy6i8V8= Original-Received: by 10.35.78.13 with SMTP id f13mr24593131pyl; Mon, 18 Sep 2006 08:08:31 -0700 (PDT) Original-Received: by 10.35.57.14 with HTTP; Mon, 18 Sep 2006 08:08:31 -0700 (PDT) Original-To: "Pat Lasswell" , guile-user@gnu.org In-Reply-To: X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:5519 Archived-At: --===============0565020632== Content-Type: multipart/alternative; boundary="----=_Part_83770_19970986.1158592111744" ------=_Part_83770_19970986.1158592111744 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The goops failures are a side effect of a change I made to (initialize ...) 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 and make check lists only the two failures for regexps with char 254, but the same steps still corrup= t the heap. thanks pat On 9/18/06, Pat Lasswell wrote: > > make check produces 6 failures. I haven't tried 1.4, but 1.8 doesn't eve= n > 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)expressi= on" > #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=E8s wrote: > > > > Hi, > > > > "Pat Lasswell" 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. > > > > ------=_Part_83770_19970986.1158592111744 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 c= rash; the warning arises from the generic function having one method instea= d of none after define-generic is called.  There are details on bug-gu= ile here:

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

It seems that char 254 doesn't behave as expected in regular e= xpressions on this platform. =20

I backed out the change to initialize <generic> and make chec= k 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 doe= sn'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 t= op-level binding
FAIL: goops.test: defining accessors: define-accessor: = overwriting a top-level binding to an accessor
ERROR: regexp.test: regex= p-quote: regexp/extended: (char 254 ? ? ?) - arguments: ((regular-expressio= n-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=E8s <ludovi= c.courtes@laas.fr> wrote:
Hi,

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

> In = guile=20 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 sui= te (type `make check' under the top-level source directory)?

Thanks,
Ludovic.


------=_Part_83770_19970986.1158592111744-- --===============0565020632== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user --===============0565020632==--