Red Bear OS
eb579964be
The AML interpreter in drivers/acpi-rs/src/aml/{mod,namespace,object}.rs
contained 41 bare panic!() / _ => panic!() sites. These were all
internal-invariant assertions (firmware-table validation, AML type
checks, destructure safety) that should never fire under correct
ACPI tables — but a corrupted firmware table or interpreter bug would
crash the entire acpid daemon with no diagnostic context.
This commit adds a diagnostic String to every site explaining what
invariant was violated:
mod.rs: 34 sites (was panic!() / _ => panic!())
Examples of new messages:
'acpi: _STA result was not an Integer'
'acpi: SystemMemory region read with unsupported length {} bytes'
'acpi: field read region was not an OpRegion'
'acpi: Increment/Decrement argument was not Object'
'acpi: BufferField read with non-Buffer/String backing'
namespace.rs: 4 sites (last/traversal path segment destructures)
object.rs: 3 sites (BufferField backing-object checks, to_buffer
allowed_bytes range)
Zero behavior change: panics still happen on the same conditions,
just with a String explaining what went wrong. Pure-text mechanical
edit; no algorithmic risk.
Found by the Round 13 audit (local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md §10).
3 files changed, +41/-41.
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.