Aren/haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
53,407 Commits 9 Branches 0 Tags 473 MiB
C++ 52.9%
C 45.9%
Assembly 0.4%
HTML 0.3%
Python 0.1%
c012e7e930
Go to file
Michael Lotz c012e7e930 libroot: Add private __arch_get_stack_trace(). 
It can be used to get a stack trace of the current thread. Note that
this works by walking frame pointers and will not produce anything
useful if an application is compiled with the frame pointers omitted.

The stack base and end addresses have to be provided as arguments and
are used to check that the frame pointers fall within that range. These
values are thread specific and can be retrieved with get_thread_info().
No other sanity checks (like checking for loops in the linked list) are
done.

This is a simplified rewrite of the stack trace code from the kernel
debugger.

As this code is common to x86 and x86_64 but is not generic across
architectures I introduced x86_common as a directory to put such
sources.
2015-04-11 23:37:54 +02:00
3rdparty checkstyle.vim: add catch to checked keywords 2014-11-26 13:27:33 +01:00
build Whitespace cleanup only. 2015-04-11 13:37:28 +02:00
data Update translations from Pootle 2015-04-11 06:27:18 +02:00
docs Haiku Book: Doxyfile: eat __attribute__ directives. 2015-04-06 18:00:39 -04:00
headers libroot: Add private __arch_get_stack_trace(). 2015-04-11 23:37:54 +02:00
src libroot: Add private __arch_get_stack_trace(). 2015-04-11 23:37:54 +02:00
.gitignore Update ACPICA to 20140724. 2014-08-23 16:30:50 +02:00
configure jam/arm: Add missing overo target board 2015-03-16 10:38:36 -05:00
Jamfile Added netcat packages for x86 and x86_64, use them. 2015-03-03 22:49:00 +01:00
Jamrules Merge branch 'gcc_syslibs' 2014-08-13 13:50:29 +02:00
makehaikufloppy Updated makehaikufloppy script, based on a patch by Rob Judd. I have no idea 2009-04-15 19:26:03 +00:00
ReadMe.Compiling Interface Guidelines: migrate to docs/, use DocBookCSS. 2015-02-12 17:08:04 -05:00
ReadMe.md ReadMe: Convert to Markdown, various cleanup. 2015-02-11 18:56:15 -05: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 OpenGrok servers:

Contributing documentation

The main piece of documentation that still needs work are the API docs (found in the tree at src/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.