This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 509
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Registers_arm_rt :wrapper class around RT's VRS RT uses REGDISPlAY structure for virtual registers set (VRS) representation. The libunwind uses Registers_* classes to hold VRS. The new class connects REGDISPlAY with libunwind Registers_* API. Also the new class reuses validRegister, validFloatRegister, getRegisterName methods from libunwind::Registres_arm class. * Methods implementation for Registers_arm_rt class * Avoid PORTABILITY_ASSERT() in StepFrame for ARM The DoTheStep accepts 3 input parameters: pc - it could be taken for regs input parameter UnwindInfoSections - is not needed in case ARM, it will be located by libunwind later, before unwinding regs - pointer to REGDISPLAY that represents RT's VRS * Remove PORTABILITY_ASSERT() in DoTheStep() SetInfoBaseOnIPRegister - sets unwind info for libunwind::UnwindCursor see UnwindCursor.hpp:1228 for additional comments * libunwind API is updated: unw_set_reg sets pointer to register value Since the unwinder must provide pointer to pc, setting only pc value in the REGDISPLAY is not enough. For this reason the libunwind should set pointers to registers to set pIP pointer. * Clean up libunwind config file The libunwind uses "if defined()" not "!()" * Initialize Registers_arm_rt with REGDISPLAY The pointer to REGDISPLAY is passed to Registers_arm_rt constructor
- Loading branch information
1 parent
e2df352
commit b059615
Showing
8 changed files
with
181 additions
and
36 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.