[Bug 283083] System goes broken after update from sources with malloc.conf
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283083] System goes broken after update from sources with malloc.conf"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 02 Dec 2024 13:30:06 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283083
Bug ID: 283083
Summary: System goes broken after update from sources with
malloc.conf
Product: Base System
Version: 14.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: bugs@FreeBSD.org
Reporter: rozhuk.im@gmail.com
Just rebuild and reinstall FBSD stable/14 and it got broken.
If I try to rebuild system after installation but before reboot I got coredump:
Core file '/tmp/install.00.core' (x86_64) was loaded.
(lldb) bt all
* thread #1, name = 'install', stop reason = signal SIGSEGV
* frame #0: 0x0000000000274f7b install`strtol + 11
frame #1: 0x000000000027ecd4 install`malloc_conf_init_helper + 2804
frame #2: 0x000000000027df39 install`malloc_init_hard_a0_locked + 137
frame #3: 0x000000000027de86 install`malloc_init_hard_a0 + 86
frame #4: 0x0000000000275c70 install`__je_bootstrap_malloc + 96
frame #5: 0x0000000000246d1e install`__libc_allocate_tls + 94
frame #6: 0x0000000000246efc install`_init_tls + 252
frame #7: 0x000000000022fcdb install`__libc_start1 + 251
frame #8: 0x0000000000223800 install`_start + 48
After reboot - it hang on kernel messages (suspect init process coredumped
too).
My /etc/malloc.conf ->
metadata_thp:disabled,retain:true,dss:disabled,narenas:8,background_thread:false,tcache:true,lg_tcache_max:16
Removing /etc/malloc.conf fix issue, but this is not best solution since other
peoples may got broken system without able to boot/login instead of some
warning message for bad malloc options.
--
You are receiving this mail because:
You are the assignee for the bug.