Copy siginfo_t to step before calling a user-space signal handler

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5769 42af7a65-404d-4744-a932-0658087f49c3

arch/arm/src/common/up_stackframe.c

@@ -96,7 +96,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/avr/src/avr/up_stackframe.c

@@ -73,7 +73,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/avr/src/avr32/up_stackframe.c

@@ -85,7 +85,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/hc/src/common/up_stackframe.c

@@ -85,7 +85,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/mips/src/common/up_stackframe.c

@@ -88,7 +88,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/sh/src/common/up_stackframe.c

@@ -84,7 +84,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/sim/src/up_stackframe.c

@@ -85,7 +85,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/x86/src/i486/up_stackframe.c

@@ -86,7 +86,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/z16/src/common/up_stackframe.c

@@ -84,7 +84,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *

arch/z80/src/common/up_stackframe.c

@@ -84,7 +84,7 @@
  *   up_use_stack() have been called but before the task has been started.
  *
  *   Thread data may be kept in the stack (instead of in the TCB) if it is
- *   accessed by the user code directory.  This includes such things as
+ *   accessed by the user code directly.  This includes such things as
  *   argv[].  The stack memory is guaranteed to be in the same protection
  *   domain as the thread.
  *