Documentation | Draft: c-user/stack_bounds_checker: Update stack checker documentation for configurable reporter (!41)

[Mohamed Hassan (@Hamzi)]

Mohamed Hassan commented on a discussion on c-user/stack_bounds_checker.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/41#note_110916

 > +is used. RTEMS provides two reporting methods: 
 > +
 > +- Default basic reporter: In the event of a blown stack, this reporter only 
 > +  calls a fatal error handler.
 > +
 > +- Detailed reporter: This reporter provides additional information, including
 > +  the task ID, name, and the stack pointer address where the stack overflow occurred.
 > +
 > +In addition, users can define their own custom reporter if needed.
 > +
 > +This set of extensions is defined as ``STACK_CHECKER_EXTENSION``.
 > +If using  ``<rtems/confdefs.h>`` for Configuration Table generation, 
 > +then all that is necessary is to define the macro ``CONFIGURE_STACK_CHECKER_ENABLED``. 
 > +If using a reporter other than the default, the application must define 
 > +``CONFIGURE_STACK_CHECKER_REPORTER`` with the name of either the detailed reporter 
 > +or a custom-defined repoter. These configurations must be set before including

Noted.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/41#note_110916
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20240813/f67dad68/attachment-0001.htm>