init.c: Change VxWorks 6 stack overflow checking for kernel apps.

2009-04-10  Ed Falis  <falis@adacore.com>

	* init.c: Change VxWorks 6 stack overflow checking for kernel apps.

	* system-vxworks-ppc.ads, system-vxworks-x86.ads: Update header.

From-SVN: r145920
This commit is contained in:
Ed Falis 2009-04-10 15:18:04 +00:00 committed by Arnaud Charlet
parent d8221f4558
commit 2c880bdfe5
4 changed files with 27 additions and 8 deletions

View File

@ -1,3 +1,9 @@
2009-04-10 Ed Falis <falis@adacore.com>
* init.c: Change VxWorks 6 stack overflow checking for kernel apps.
* system-vxworks-ppc.ads, system-vxworks-x86.ads: Update header.
2009-04-10 Thomas Quinot <quinot@adacore.com>
* sem_ch6.ads (Check_Subtype_Conformant): Add ??? comment for

View File

@ -1782,8 +1782,9 @@ getpid (void)
}
#endif
/* VxWorks expects the field excCnt to be zeroed when a signal is handled.
The VxWorks version of longjmp does this; GCC's builtin_longjmp doesn't. */
/* VxWorks 653 vThreads expects the field excCnt to be zeroed when a signal is.
handled. The VxWorks version of longjmp does this; GCC's builtin_longjmp
doesn't. */
void
__gnat_clear_exception_count (void)
{
@ -1822,19 +1823,31 @@ __gnat_map_signal (int sig)
msg = "SIGBUS: possible stack overflow";
break;
#else
#ifdef __RTP__
/* In RTP mode a SIGSEGV is most likely due to a stack overflow,
since stack checking uses the probing mechanism. */
#if (_WRS_VXWORKS_MAJOR = 6)
case SIGILL:
exception = &constraint_error;
msg = "SIGILL";
break;
#ifdef __RTP__
/* In RTP mode a SIGSEGV is most likely due to a stack overflow,
since stack checking uses the probing mechanism. */
case SIGSEGV:
exception = &storage_error;
msg = "SIGSEGV: possible stack overflow";
break;
#else
/* In kernel mode a SIGILL is most likely due to a stack overflow,
/* VxWorks 6 kernel mode with probing. SIGBUS for guard page hit */
case SIGSEGV:
exception = &program_error;
msg = "SIGSEGV";
break;
case SIGBUS:
exception = &storage_error;
msg = "SIGBUS: possible stack overflow";
break;
#endif
#else
/* VxWorks 5: a SIGILL is most likely due to a stack overflow,
since stack checking uses the stack limit mechanism. */
case SIGILL:
exception = &storage_error;

View File

@ -5,7 +5,7 @@
-- S Y S T E M --
-- --
-- S p e c --
-- (VxWorks Version PPC) --
-- (VxWorks 5 Version PPC) --
-- --
-- Copyright (C) 1992-2009, Free Software Foundation, Inc. --
-- --

View File

@ -5,7 +5,7 @@
-- S Y S T E M --
-- --
-- S p e c --
-- (VxWorks Version x86) --
-- (VxWorks 5 Version x86) --
-- --
-- Copyright (C) 1992-2009, Free Software Foundation, Inc. --
-- --