Go to file
Ingo Weinhold 467fe4ca0c kernel: Add core dump facility
* Add function core_dump_write_core_file(). It writes a core file for
  the current thread's team. The file format is similar to that of
  other OSs (i.e. ELF with PT_LOAD segments and a PT_NOTE segment), but
  most of the notes are Haiku specific (infos for team, areas, images,
  threads). More data will probably need to be added.
* Add team flag TEAM_FLAG_DUMP_CORE, thread flag
  THREAD_FLAGS_TRAP_FOR_CORE_DUMP, and Team property coreDumpCondition,
  a condition variable available while a core dump is progress. A
  thread that finds its flag THREAD_FLAGS_TRAP_FOR_CORE_DUMP set before
  exiting the kernel to userland calls core_dump_trap_thread(), which
  blocks on the condition variable until the core dump has finished. We
  need the team's threads to stop so we can get their CPU state (and
  have a generally unchanging team state while writing the core file).
* Add user debugger message B_DEBUG_WRITE_CORE_FILE. It causes
  core_dump_write_core_file() to be called for the team.
* Dumping core as an immediate effect of a terminal signal has not been
  implemented yet, but that should be fairly straight forward.
2016-04-24 18:22:14 +02:00
3rdparty dev-perso: check for a TODO list and print first 5 items 2016-01-07 23:23:11 +01:00
build bluetooth: Re-introduce to image 2016-04-22 14:55:55 -05:00
data Update translations from Pootle 2016-04-09 07:22:44 +02:00
docs BColorControl docs: pointer style 2016-03-12 19:10:39 -08:00
headers kernel: Add core dump facility 2016-04-24 18:22:14 +02:00
src kernel: Add core dump facility 2016-04-24 18:22:14 +02:00
.gitignore .gitignore: add .pyc and .pyo files. 2015-06-19 15:40:40 -04:00
configure configure: Add host as valid build target in help. 2015-12-15 21:02:02 -05:00
Jamfile Switch to tiff4 as system dependency. 2015-10-18 10:00:02 +02:00
Jamrules build: delete DocumentationRules. 2015-06-22 13:20:07 -04:00
LICENSE Add a LICENSE file 2015-11-16 21:51:33 +01:00
ReadMe.Compiling.md Added hint to have an updated "bison" for compiling on OS X 2015-12-22 17:46:39 +01:00
ReadMe.md ReadMe: HaikuPorts has moved to GitHub. 2015-06-30 10:03:49 -04:00

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 OpenGrok servers:

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.