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

The Haiku operating system

Go to file

KENZ dca65c878f Debugger: just skip .debug_frame/.eh_frame section contains a 0-length CIE Some executables (or shared objects) may have .debug_frame or .eh_frame section which contains the CIE(/FDE) length is 0. The DWARF spec doesn't describe this case explicitly, but doesn't prohibit it. LSB says to treat this a terminator of the CIE. https://refspecs.linuxbase.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/ehframechpt.html Previous code failed to load the entire debug info of the executable. New code just skip these section (don't read anymore) after the Debugger (kit) encounter a 0-length CIE. Fixes #18438. Change-Id: I382d0ec409d40570b5bccd384d38fa3c29ae2e7f Reviewed-on: https://review.haiku-os.org/c/haiku/+/6538 Reviewed-by: Rene Gollent <rene@gollent.com> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> (cherry picked from commit `f0e9ed4488`) Reviewed-on: https://review.haiku-os.org/c/haiku/+/7016 Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>		2023-10-07 19:26:04 +00:00
3rdparty	script to parse supported ids for network drivers	2022-10-25 19:09:28 +00:00
build	HaikuPorts: Synchronize.	2022-12-16 21:29:47 +00:00
data	Update translations from Pootle	2022-12-17 08:26:02 +00:00
docs	View: provide the transform between different coordinate spaces	2022-11-13 04:04:52 +00:00
headers	headers/os: Bump max gcc to 13.x	2023-07-01 23:31:39 +00:00
src	Debugger: just skip .debug_frame/.eh_frame section contains a 0-length CIE	2023-10-07 19:26:04 +00:00
.editorconfig	editorconfig: Add new config file around our unique style	2017-09-26 14:22:32 -05:00
.gitignore	gitignore: Add Visual Studio Code and IntelliJ IDEA configuration directories	2021-05-31 20:15:44 +00:00
.gitreview	gerrit: Add .gitreview config	2018-01-04 00:04:02 -06:00
configure	cross_tools: allow specifying a custom sysroot path	2022-06-05 09:08:20 +00:00
Jamfile	Update build-packages for GCC 11 upgrade.	2021-12-07 14:26:24 -05:00
Jamrules	Revert "Jamrules: Include the UserBuildConfig before processing repositories."	2019-09-15 17:33:36 +02:00
lgtm.yml	lgtm.yml: disable Wformat-diag when building gcc	2021-12-14 06:06:41 +00: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	Added missing --cross-tools-source argument name for bootstrap build and missing \ at the end of line 136	2021-12-02 08:05:50 +00: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.