Augustin Cavalier
91eb43cfc0
The case where no BApplication has been created at the time of fork is not blocked by this change (as it might be useful in fork-to-background before creating a BApplication.) Reinitializing or recreating a BApplication where one already exists, though, is not supported by the kits, and just leads to problems. And when the global destructors are invoked after a fork, such as by exit(), then the parent team's state may be corrupted due to the deletion of BLocker semaphores or other global state. So, we thus set be_app to an invalid pointer, and if terminate_after() is called with this pointer, we invoke debugger(). (We should really just prevent semaphores from being used across processes unless explicitly specified, but that would be an API compatibility break from BeOS, so we'll need to do it carefully, or not until after R1.) Would have clearly caught the problem in #18576 and the linked thread.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://grok.nikisoft.one/opengrok/ (OpenGrok, provided by Niklas Poslovski)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.