Fork us on GitHub Follow us on Google+ Follow us on Facebook Follow us on Twitter

Changes between Initial Version and Version 6 of Ticket #310


Ignore:
Timestamp:
2013-03-28T17:23:01Z (5 years ago)
Author:
Martin Decky
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #310

    • Property Keywords gsoc12 gsoc13 added
    • Property Type changed from defect to enhancement
    • Property Component changed from unspecified to debugging
    • Property Milestone changed from 0.5.0 to
  • Ticket #310 – Description

    initial v6  
    22
    33 Details::
    4  The DWARF Debugging Information Format is a rich, processor architecture independent debugging format supported by the toolchain used to build HelenOS. It encodes information that may otherwise be hard or impossible to get during HelenOS run-time. The goal of this project is to identify aspects of the DWARF format that would improve the debugging capabilities and observability of both the HelenOS kernel and applications, and bring support for those aspects to HelenOS. An example of such an aspect is the support for reliable call stack unwinding.
     4  The DWARF Debugging Information Format is a rich, processor architecture independent debugging format supported by the toolchain used to build HelenOS. It encodes information that may otherwise be hard or impossible to get during HelenOS run-time. The goal of this project is to identify aspects of the DWARF format that would improve the debugging capabilities and observability of both the HelenOS kernel and applications, and bring support for those aspects to HelenOS. An example of such an aspect is the support for reliable call stack unwinding.
    55
    66 What Gains and Benefits will this bring?::
    7  Besides other possible benefits that depend on the supported features, one key benefit would be the ability to reliably generate stack traces on some architectures that are not stacktracing-friendly, such as mips32.
     7  Besides other possible benefits that depend on the supported features, one key benefit would be the ability to reliably generate stack traces on some architectures that are not stacktracing-friendly, such as mips32.
    88
    99 Difficulty::
    10  medium
     10  Medium
    1111
    1212 Required skills::
    13  A successful applicant will have good skills of programming in the C language and at least basic familiarity with binutils, gcc and linker scripts. This project may expose the candidate to mips32 assembly.
     13  A successful applicant will have good skills of programming in the C language and at least basic familiarity with binutils, gcc and linker scripts. This project may expose the candidate to mips32 assembly.
    1414
    1515 Documentation::
     
    2020 
    2121 Possible mentors::
    22  HelenOS Core Team, Jakub Jermar
     22  HelenOS Core Team, Jakub Jermar