Augustin Cavalier
3280d3c47d
This reverts3a81e9446d(2022). That commit fixed #17556 by just checking if the area had an underlying cache that wasn't a RAM cache. But there are cases where there will be RAM source caches that we have to take into account, too, not just vnode caches or the like. The most common example of that would be all areas of a team after a fork(); the original pages will be in a read-only source cache. This commit fixes the real underlying problem: if the first area has a source cache, then the new second cache needs to have that as its source, too; and furthermore must have the correct offsets in order to access its pages correctly. The test for #17556 that was added in9ed77019b6still works as before, as do all the applications I tested that use cut_area. Some assertion failures that the cut tests triggered (related to commitment sizes) are fixed by this, as well. This also seems to fix the remaining instability on fork() in the boehm-gc's "gctest".
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://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- 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.