UBSAN report for main [so: 14] zpool status -x : applying non-zero offset 4 to null pointer

# zpool status -x all pools are healthy /usr/main-src/sys/contrib/openzfs/module/nvpair/nvpair.c:3129:49: runtime error: applying non-zero offset 4 to null pointer SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /usr/main-src/sys/contrib/openzfs/module/nvpair/nvpair.c:3129:49 in For re

ASAN&UBSAN world in chroot tree, ports built previously, variable results finding /usr/local/lib/*.so* files

Note: like the /usr/local/lib/*.so* files, the wget and git were built previously to the existence of the ASAN&UBSAN world. chrooted into the world I built with ASAN and UBSAN: # ldd `which wget` /usr/local/bin/wget: libintl.so.8 => /usr/local/lib/libintl.so.8 (0x800edc000) libuni

Re: UBSAN report for main [so: 14] zpool status -x : applying non-zero offset 4 to null pointer

On 2022-Jan-14, at 01:50, Mark Millard wrote: > # zpool status -x > all pools are healthy > /usr/main-src/sys/contrib/openzfs/module/nvpair/nvpair.c:3129:49: runtime > error: applying non-zero offset 4 to null pointer > SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior > /usr/main-src/sys

An explanation of some "Container overflow" ASAN reports

Looks like libc++ does the following sort of thing (from lldb list): . . . 1635 1636 template 1637 template 1638 void 1639 #ifndef _LIBCPP_CXX03_LANG (lldb) 1640 vector<_Tp, _Allocator>::__push_back_slow_path(_Up&& __x) 1641 #else 1642 vector<_Tp, _Allocator>::__push_ba

Re: An explanation of some "Container overflow" ASAN reports: libc++ does sometimes temporarily overflow the used range of a container

> On 2022-Jan-14, at 04:44, Mark Millard wrote: > > Looks like libc++ does the following sort of thing > (from lldb list): > > . . . > 1635 > 1636template > 1637template > 1638void > 1639#ifndef _LIBCPP_CXX03_LANG > (lldb) > 1640vect

UBSAN reported behaviors in view use: Null pointer use oddities in contrib/nvi/... code

# env ASAN_OPTIONS=detect_container_overflow=0 lldb view (lldb) target create "view" Current executable set to 'view' (x86_64). (lldb) run /usr/main-src/contrib/nvi/common/log.c Process 96507 launched: '/usr/bin/view' (x86_64) Process 96507 stopped * thread #1, name = 'view', stop reason = Nullptr

Re: UBSAN reported behaviors in view use: Null pointer use oddities in contrib/nvi/... code

+ CC upstream On Fri, Jan 14, 2022 at 05:37:20AM -0800, Mark Millard wrote: > # env ASAN_OPTIONS=detect_container_overflow=0 lldb view > (lldb) target create "view" > Current executable set to 'view' (x86_64). > (lldb) run /usr/main-src/contrib/nvi/common/log.c > Process 96507 launched: '/usr/bin/

Re: Dell Latitude 7400 - nvme0: Missing interrupt

вс, 17 окт. 2021 г. в 17:52, Pavel Timofeev : > > > вс, 17 окт. 2021 г. в 11:19, Alexander Motin : > >> It may be a noise, but comparing logs I see in reboot case also >> "acpi_ec0: not getting interrupts, switched to polled mode". I am >> thinking whether the problem may be caused not by SSD, bu

ASAN: "ls -l, *" AddressSanitizer warning: "unexpected format specifier in printf interceptor: %*j'"

# ls -l, * /usr/main-src/lib/libc/stdio/fread.c:133:10: runtime error: applying zero offset to null pointer SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /usr/main-src/lib/libc/stdio/fread.c:133:10 in ==47404==AddressSanitizer: WARNING: unexpected format specifier in printf intercepto

Re: git: 4a864f624a70 - main - vm_pageout: Print a more accurate message to the console before an OOM kill

Thanks. This will allow me to remove part of my personal additions in this area --and my having to explain the misnomer when trying to help someone analyze why they end up with OOM activity so they can figure out what to do about it. There seem to be two separate sources of VM_OOM_SWAPZ. Showing m