Opened 4 months ago
Closed 2 months ago
#19003 closed bug (not reproducible)
app_server won't load on boot randomly
Reported by: | madmax | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | - General | Version: | R1/beta5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
32-bit hrev57982 on qemu launched with:
qemu-kvm -vga virtio -m 8G -smp 8 -machine q35 -cpu kvm64 -nic user,model=pcnet -hda ./32bits.qcow2 -hdb ./ports.qcow2
.
Sometimes stops booting in rocket icon. Serial shows:
runtime_loader: /boot/system/lib/x86/libbsd.so: Could not resolve symbol '_ZSt7nothrow' runtime_loader: /boot/system/lib/x86/libbsd.so: Troubles relocating: Symbol not found runtime_loader: /boot/system/lib/x86/libbsd.so: Could not resolve symbol '_ZSt7nothrow' runtime_loader: /boot/system/lib/x86/libbsd.so: Troubles relocating: Symbol not found Launching x-vnd.haiku-app_server failed: Symbol not found runtime_loader: /boot/system/lib/x86/libbsd.so: Could not resolve symbol '_ZSt7nothrow' runtime_loader: /boot/system/lib/x86/libbsd.so: Troubles relocating: Symbol not found
Unfortunately it happens very seldom. Didn't trigger with hrev57903 and hrev57980, though probably I was just lucky with the latter.
Attachments (1)
Change History (4)
comment:1 by , 4 months ago
by , 4 months ago
Attachment: | hrev57982 app_server fail.txt added |
---|
comment:2 by , 4 months ago
Hadn't noticed that detail. The messages were just together at the end of the log, maybe the libbsd ones are from another executable.
I've booted and rebooted that same VM some 40 times today with no crash.
Note:
See TracTickets
for help on using tickets.
Why is GCC2 app_server trying to load a modern-GCC libbsd? Or are the messages unrelated somehow?