<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 17/04/2020 19:30, Gedare Bloom wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAC82fA1Pi+AT53hpGE5B=7EUDbzDpYkgBKtTa=Rydgb1Sx2kuA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">On Fri, Apr 17, 2020 at 2:11 AM Sebastian Huber
<a class="moz-txt-link-rfc2396E" href="mailto:sebastian.huber@embedded-brains.de" moz-do-not-send="true"><sebastian.huber@embedded-brains.de></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">Close #3953.
---
c-user/user_extensions.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/c-user/user_extensions.rst b/c-user/user_extensions.rst
index c3bd1c6..89b86fd 100644
--- a/c-user/user_extensions.rst
+++ b/c-user/user_extensions.rst
@@ -466,6 +466,8 @@ DIRECTIVE STATUS CODES:
* - ``RTEMS_SUCCESSFUL``
- extension set created successfully
+ * - ``RTEMS_INVALID_ADDRESS``
+ - ``table`` or ``id`` are NULL
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">This is OK, I guess there are no other valid checks that are made on
addresses usually.
As we continue to improve our processes, it may be worth considering
the use of well-defined regions and symbol ranges to provide
additional sanity checks on address pointers, maybe. I'm just
ruminating.
</pre>
</blockquote>
Actually I think that all these NULL pointer checks are completely
superfluous. However, since most RTEMS APIs have them I thought it
would be consistent to add this also here.<br>
</body>
</html>