mirror of https://review.haiku-os.org/haiku synced 2025-01-18 12:38:51 +01:00

The Haiku operating system

Go to file

Augustin Cavalier 62c620c57d kernel/x86: Rework handling of %edx in syscall handler (again.) The previous change to this logic (`9921f44462`) apparently caused intermittent crashes with various applications. It seems that EDX is not expected to be clobbered by functions that do not have 64-bit return values, and if it is, crashes result, like #19024. This commit reworks the logic to not change %edx in the iframe at all if we don't have a 64-bit return value, and then adjusts the debug logic to clear %edx before invoking the post-syscall debugger hook. This means we have to run the post-syscall debugger hook before clearing the flags, but that should be fine (and perhaps even useful.) Fixes #19024, and possibly other crashes that have cropped up on 32-bit x86 in the last few weeks, at least. Change-Id: I3280033bc2dd05aca254555d6ee3b173a270ebf9 Reviewed-on: https://review.haiku-os.org/c/haiku/+/8158 Haiku-Format: Haiku-format Bot <no-reply+haikuformatbot@haiku-os.org> Reviewed-by: Michael Lotz <mmlr@mlotz.ch> (cherry picked from commit `63b183cd7c`) Reviewed-on: https://review.haiku-os.org/c/haiku/+/8128 Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>		2024-09-02 15:16:57 +00:00
3rdparty	proj2make: some minor improvements.	2024-07-02 15:39:43 +00:00
build	DefaultBuildProfiles: We now have Python 3.10.	2024-08-13 00:10:27 +00:00
data	Update translations from Pootle	2024-08-29 19:33:15 -04:00
docs	Input server: add mouse-specific API for button map and click speed	2024-07-29 17:30:39 +00:00
headers	libnetwork: Only build BeOS compatibility code if _BEOS_R5_COMPATIBLE_ is set.	2024-08-29 19:30:56 +00:00
src	kernel/x86: Rework handling of %edx in syscall handler (again.)	2024-09-02 15:16:57 +00:00
.editorconfig	editorconfig: Add new config file around our unique style	2017-09-26 14:22:32 -05:00
.gitignore	docs/develop/ide: A quick guide for haiku code completion	2023-12-05 20:02:07 +00:00
.gitreview	gerrit: Add .gitreview config	2018-01-04 00:04:02 -06:00
configure	configure: Remove support for HOST_CC_IS_LEGACY_GCC.	2024-07-24 21:33:57 -04:00
Jamfile	Updates in preparation for package sync on gcc2h.	2024-08-10 21:37:15 +00:00
Jamrules	Revert "Jamrules: Include the UserBuildConfig before processing repositories."	2019-09-15 17:33:36 +02:00
License.md	LICENSE: Rename to License.md, and remove all licenses but the MIT.	2016-07-29 17:36:17 -04:00
ReadMe.Compiling.md	Readme.Compiling.md: Mention the need for zstd and python3	2023-11-18 14:58:01 +01:00
ReadMe.md	ReadMe: Add Getting Involved link	2021-06-13 21:06:58 +00:00

ReadMe.md

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.