[Bug 2080] New: Fatal error user extension exposes internal score Internal_errors_Source enum.

bugzilla-daemon at rtems.org bugzilla-daemon at rtems.org
Thu Nov 15 20:48:44 UTC 2012


https://www.rtems.org/bugzilla/show_bug.cgi?id=2080

             Bug #: 2080
           Summary: Fatal error user extension exposes internal score
                    Internal_errors_Source enum.
    Classification: Unclassified
           Product: RTEMS
           Version: unknown
          Platform: All
        OS/Version: RTEMS
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpukit
        AssignedTo: joel.sherrill at oarcorp.com
        ReportedBy: chrisj at rtems.org


The fatal error user extension as shown here:

http://www.rtems.org/onlinedocs/releases/rtemsdocs-4.10.2/share/rtems/html/c_user/c_user00406.html

references 'Internal_errors_Source' which is an internal score enum.

This interface should not be exposed this way and a "classic" api interface
should be provided and the error states documented in the user manual.

The enum, its location and what it is used for is causing problems where
changes such as:

http://git.rtems.org/rtems/commit/cpukit/score/include/rtems/score/interr.h?id=038e2f4a8825b8367a2b0102afdb017f0281deeb

are being applied. The change itself is valid because adding a way for an
application to raise an error is important how-ever it is breaking the
isolation of the score.

Maybe the error source enum value path in the score is changed to uint32_t and
bit masked where the a bit states the usage, ie internal or external and then
the remainder is a value. This removes the need for exporting a internal type
from the score and allows the classic API to grow as it needs without the score
being concerned.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the bugs mailing list