Mohamed Hassan commented on a discussion on spec/acfg/if/stack-checker-reporter.yml: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/4#note_111304 > +enabled-by: true > +index-entries: > +- stack checker reporter > +interface-type: appl-config-option > +links: > +- role: interface-placement > + uid: domain > +- role: interface-ingroup > + uid: group-stack-checker > +- role: constraint > + uid: ../constraint/init-stack-checker-reporter > +name: CONFIGURE_STACK_CHECKER_REPORTER > +notes: | > + This configuration option works in conjunction with > + ${stack-checker-enabled:/name}. If the stack checker is not enabled, > + configuring stack reporter will result in a C preprocessor error. Yeah understood. My initial thought was that if someone deliberately configures the stack checker reporter without enabling the stack checker, they might need a clear an alarm. it can be changed to a warning. -- View it on GitLab: https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/4#note_111304 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
