amd64/163710: setjump in causes stack corruption

Russell Cattelan cattelan at
Fri Mar 16 17:20:03 UTC 2012

The following reply was made to PR amd64/163710; it has been noted by GNATS.

From: Russell Cattelan <cattelan at>
To: Peter Wemm <peter at>
Cc: freebsd-gnats-submit at
Subject: Re: amd64/163710: setjump in causes stack corruption
Date: Fri, 16 Mar 2012 12:12:27 -0500

 This is a multi-part message in MIME format.
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: 7bit
 Hash: SHA1
 On 3/16/12 11:56 AM, Peter Wemm wrote:
 > On Thu, Mar 15, 2012 at 2:40 PM, Russell Cattelan
 > <cattelan at> wrote:
 >> The following reply was made to PR amd64/163710; it has been
 >> noted by GNATS.
 > [..]
 >> Does the last patch seem acceptable?
 >> Can we close this issue out?
 > Sadly not,
 > +no-machine: + rm -f   ${.CURDIR}/../../ficl/machine
 > .. this is definitely bogus no matter what. This attempts to
 > modify the source tree which may be read only, and should never
 > even have a "machine->..." symlink in it to remove in the first
 > place.
 The sym link is created by the build of ficl for the loader.
 See: boot/ficl/Makefile
 	ln -sf ${.CURDIR}/../../i386/include machine
 Are you suggesting that is incorrect and should be fixed?
 > I see sys/boot/userboot/ficl/Makefile has commented out the code
 > that sets up the ./machine links in its ${.OBJDIR} and there's -I
 > paths all over the place so my guess is that it's picking up some
 > of the i386 machine links rather than setting up its own.  You
 > probably need to look at the userboot/ficl/Makefile code and make
 > sure its setting up the correct links rather than accidently using
 > one belonging to something else.
 Well let me explain this again.
 If the build is done from scratch things work because
 boot/userboot/ficl is built before boot/ficl.
 If an incremental build is done (e.g. when doing devel on the userboot
 lib) boot/userboot/ficl will end up picking up i386 header files due
 to the symlink that was created by boot/ficl/Makefile
 I'll will grant you this bug isn't hit by a normal full build due
 to way the build it ordered.
 The problem is incremental builds, that IMHO shouldn't be creating
 a bad lib.
 > Or your source tree is contaminated somehow with a machine-> link 
 > somewhere that it isn't supposed to be.
 The problems exists in a stock freebsd src tree this is not a problem
 created by anything I'm working on.
 - -Russell
 Version: GnuPG v1.4.11 (Darwin)
 Comment: Using GnuPG with Mozilla -
 Content-Type: text/x-vcard; charset=utf-8;
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 fn:Russell Cattelan
 email;internet:cattelan at
 tel;cell:612 805 3144

More information about the freebsd-amd64 mailing list