From owner-freebsd-ports Thu Mar 16 23: 7:48 2000 Delivered-To: freebsd-ports@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 5F29C37B7B7; Thu, 16 Mar 2000 23:07:38 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id IAA22614; Fri, 17 Mar 2000 08:07:36 +0100 (CET) (envelope-from asmodai) Date: Fri, 17 Mar 2000 08:07:36 +0100 From: Jeroen Ruigrok van der Werven To: Satoshi - Ports Wraith - Asami Cc: John Polstra , ports@FreeBSD.org, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: ports/devel/boehm-gc/patches patch-aa Message-ID: <20000317080736.B22536@lucifer.bart.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from asami@FreeBSD.org on Thu, Mar 16, 2000 at 06:11:34PM -0800 Organisation: bART Internet Services B.V. Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000317 03:15], Satoshi - Ports Wraith - Asami (asami@FreeBSD.org) wrote: > * From: John Polstra > > * Satoshi - Ports Wraith - Asami wrote: > * > * From: Jeroen Ruigrok van der Werven > >Ok, but my observation contradicts asmodai's findings. Both the PR >and asmodai reports this error on 3-stable, and asmodai said mktable >segfaults under 4-{current,stable}. I saw this on 4-current (actually >4.0-release, this is the package building machine). Yeah ok, but I also did this on this 5.0 box (which isn't that different from 4.0-RELEASE/4.0-CURRENT) at this moment and that solves my problems. Keeping the rev 1.5 patch-aa on my 5.0 box does indeed yield the same problem as on STABLE (I erroneously thought it segfaulted). > * > now that I've reverted patch-aa to rev. 1.4 and rebuilt the boehm-gc > * > package, this is what I get. > * > > * > === > * > : > * > ./mktable 100 tagtable.tab > tagtable.c > * > Segmentation fault - core dumped > * > *** Error code 139 > * > * Hmm, that I don't understand. The guy who filed the PR said that > * reverting patch-aa made it all work for him. He's running > * 3.4-stable from March 4, by the way. > >This looks like what asmodai reported on 4-{current,stable}. No, I retested, and I get the same problem as with 3.4-STABLE, that bogus characters get inserted into tagtable.c. I wonder. My CFLAGS/COPTFLAGS are set to -O2 -g -pipe, so it might be the debugging symbols which stabilise the app. I have seen often before. >By the way, I repeated the tests on a 3-stable chroot environment (on >a 4-current machine), and it fixed the w3m and ja-w3m builds. Good. But I am still wondering where the segfaults come from... -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA NET.WORKS The Netherlands BSD: Technical excellence at its best http://www.bart.nl Trying to fool myself with Dreams that never come true... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message