Date: Thu, 22 Oct 2020 13:15:17 +0000 From: bugzilla-noreply@freebsd.org To: amd64@FreeBSD.org Subject: [Bug 163710] setjump in userboot.so causes stack corruption Message-ID: <bug-163710-17361-NVl4bMMKgc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-163710-17361@https.bugs.freebsd.org/bugzilla/> References: <bug-163710-17361@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D163710 DontWorry <abhkamal0512@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abhkamal0512@gmail.com --- Comment #16 from DontWorry <abhkamal0512@gmail.com> --- (In reply to peter from comment #7) On Thu, Mar 15, 2012 at 2:40 PM, Russell Cattelan <cattelan@thebarn.com> wr= =3D ote: > The following reply was made to PR amd64/163710; it has been noted by GNA= =3D TS. [..] > =3DA0Does the last patch seem acceptable? > > =3DA0Can 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. 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. Or your source tree is contaminated somehow with a machine-> link somewhere that it isn't supposed to be. --=3D20 Peter Wemm - peter@wemm.org; https://www.manganelo.link/; peter@yahoo-inc.c= om; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell --------------------------------------------------------------------------- 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-163710-17361-NVl4bMMKgc>