On Tue, Jul 14, 2015 at 12:14:08PM -0500, Josh Poimboeuf wrote:
> This adds a CONFIG_STACK_VALIDATION option which enables a host tool
> named stackvalidate which runs at compile time. It analyzes every .o
> file and ensures the validity of its stack metadata. It enforces a set
> of rules on asm code and C inline assembly code so that stack traces can
> be reliable.
>
> Currently it checks frame pointer usage. I plan to add DWARF CFI
> validation as well.
Validation or Annotation, as in the generation of DWARF CFI info?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> This adds a CONFIG_STACK_VALIDATION option which enables a host tool
> named stackvalidate which runs at compile time. It analyzes every .o
> file and ensures the validity of its stack metadata. It enforces a set
> of rules on asm code and C inline assembly code so that stack traces can
> be reliable.
>
> Currently it checks frame pointer usage. I plan to add DWARF CFI
> validation as well.
Validation or Annotation, as in the generation of DWARF CFI info?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/