[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-amd64
Subject:    [Bug 163710] setjump in userboot.so  causes stack corruption
From:       bugzilla-noreply () freebsd ! org
Date:       2020-10-22 13:15:17
Message-ID: bug-163710-17361-NVl4bMMKgc () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id3710

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> wrote:
> The following reply was made to PR amd64/163710; it has been noted by GNA
TS.
[..]
>  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.

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.
-- 
Peter Wemm - peter@wemm.org; https://www.manganelo.link/; peter@yahoo-inc.com;
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.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]