When python3.?-config is symlinked to another location it starts
outputting bogus paths. For example
$ pwd
/home/tobias
$ python3.6-config --includes
-I/usr/local/include/python3.6m -I/usr/local/include/python3.6m
$ ln -s /usr/local/bin/python3.6-config python3-config
$ ./python3-config --includes
-I/home/include/python3.6m -I/home/include/python3.6m
This breaks ports trying to use BINARY_ALIAS together with
python3.?-config. Apply a patch to resolve the symlink first before
trying to find the install prefix.
PR: 229749
Submitted by: tobik
Reviewed by: antoine, miwi
Approved by: python (miwi)
- devel/binutils: Remove i386 a.out linker scripts when building
i386-binutils or a base/binutils that targets i386.
- devel/powerpc64-gcc: Remove float.h on i386 since it conflicts
with sys/x86/include/float.h.
- devel/i386-{binutils,gcc,xtoolchain}: New ports.
Reviewed by: bapt (previous version)
Differential Revision: https://reviews.freebsd.org/D16228
- Improve fallback handling for the read of pcb_size.
If for some reason kgdb has only the kernel's debug info, a read of
pcb_size will simply return 0, resulting in an exception when unwinding
the stack of a thread that was on a CPU at the time the dump was
created. In this case, fall back to using sizeof(struct pcb).
- Always supply a value for the PC register on x86.
A thread's PCB may have been swapped out, and a dummy value ensures that
we don't get an exception while enumerating threads in a dump.
- Mark all 64-bit address bits as valid for aarch64 kernels.
ARMv8 supports pointer tagging in which case the upper 8 bits of VAs are
ignored, but FreeBSD kernels are linked such that they depend on those
upper 8 bits being set to 1. GDB was stripping those bits by default
causing KVAs to be mapped to invalid addresses.
- Rework kgdb -w support to only open /dev/mem writable.
Don't depend on the gdb global 'write_files' option which tries to
rewrite the kernel binary on close which can crash. Instead, add an
optional '-w' flag to 'target vmcore' which opens the vmcore with
O_RDWR instead of O_RDONLY. Change the kgdb '-w' option to set this
flag in the nested 'target vmcore' command rather than passing the
global '-w' option to gdb.
- Garbage collect old code for reading dumptid.
- First cut at FreeBSD/arm kernel support.
Tested on live kernel on my RPi, but not against a crashdump, and only
trapframes from userland, not a nested trap.
Submitted by: markj (1, 2)
Approved by: kan
Differential Revision: https://reviews.freebsd.org/D16013
- Project has moved to GitHub
- Pass maintainership to submitter
PR: 229015
Submitted by: Trenton Schulz <trueos@norwegianrockcat.com>
Approved by: pi (mentor)
