Comtrol eCos - Manual (Page 456)

Chapter 31. POSIX Standard Support
unsigned int sleep( unsigned int seconds );
Functions Omitted
pid_t fork(void);
int execl( const char ∗ path, const char ∗ arg, ... );
int execv( const char ∗ path, char ∗ const argv[] );
int execle( const char ∗ path, const char ∗ arg, ... );
int execve( const char ∗ path, char ∗ const argv[],
char ∗ const envp[] );
int execlp( const char ∗ path, const char ∗ arg, ... );
int execvp( const char ∗ path, char ∗ const argv[] );
int pthread_atfork( void( ∗ prepare)(void),
void ( ∗ parent)(void),
void ( ∗ child)() );
pid_t wait( int ∗ stat_loc );
pid_t waitpid( pid_t pid, int ∗ stat_loc,
int options );
void _exit( int status );
Notes
• Signal handling may be enabled or disabled with the CYGPKG_POSIX_SIGNALS option. Since signals are
used by other POSIX components, such as timers, disabling signals will disable those components too.
• kill() and sigqueue() may only take a pid argument of zero, which maps to the current process.
• The SIGEV_THREAD notification type is not currently implemented.
• Job Control and Memory Protection signals are not supported.
• An extra implementation defined si_code value, SI_EXCEPT, is defined to distinguish hardware generated
exceptions from others.
• Extra signals are defined: _SIGTRAP_,_SIGIOT_, _SIGEMT_, and _SIGSYS_. These are largely to maintain
compatibility with the signal numbers used by GDB.
• Signal delivery may currently occur at unexpected places in some API functions. Using longjmp() to transfer
control out of a signal handler may result in the interrupted function not being able to complete properly. This
may result in later function calls failing or deadlocking.
Process Environment [POSIX Section 4]
Functions Implemented
int uname( struct utsname ∗ name );
time_t time( time_t ∗ tloc );
char ∗ getenv( const char ∗ name );
352