Known Issues - Revision history

Wheirman at 16:47, 16 December 2011

2011-12-16T16:47:56Z

Wheirman at 13:12, 14 December 2011

2011-12-14T13:12:48Z

Wheirman at 15:20, 5 December 2011

2011-12-05T15:20:30Z

Wheirman: moved Unsupported Application Behavior to Known Issues

2011-12-05T15:20:14Z

moved Unsupported Application Behavior to Known Issues

Tcarlson at 02:59, 16 November 2011

2011-11-16T02:59:29Z

Wheirman at 19:59, 15 November 2011

2011-11-15T19:59:28Z

Wheirman: Created page with "Sniper does currently not support the following application behavior: * Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)"

2011-11-12T17:36:57Z

Created page with "Sniper does currently not support the following application behavior: * Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)"

New page

Sniper does currently not support the following application behavior:

* Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)

← Older revision		Revision as of 16:47, 16 December 2011
Line 5:		Line 5:
	* Spawning more application threads than simulated cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.		* Spawning more application threads than simulated cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.

−	* ~~Instruction~~ exceptions, such as SIGFPE, SIGSEGV ~~and~~ other synchronous signals ~~(internal bug #121)~~	+	* If your application is expected to encounter and recover from instruction exceptions, such as SIGFPE, SIGSEGV or other synchronous signals, you'll need to add the <code>-g --general/enable_signals=true</code> command-line parameter.

← Older revision		Revision as of 13:12, 14 December 2011
Line 5:		Line 5:
	* Spawning more application threads than simulated cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.		* Spawning more application threads than simulated cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.

−	* Instruction exceptions (such as SIGFPE, SIGSEGV~~), use of~~ signals (internal bug #121)	+	* Instruction exceptions, such as SIGFPE, SIGSEGV and other synchronous signals (internal bug #121)

← Older revision		Revision as of 15:20, 5 December 2011
Line 1:		Line 1:
		+	==Unsupported Application Behavior==
		+
	Sniper does currently not support the following application behavior:		Sniper does currently not support the following application behavior:

@@ Line 1: / Line 1: @@
 Sniper does currently not support the following application behavior:
-* Spawning more threads than cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.
+* Spawning more application threads than simulated cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.
 * Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)

← Older revision		Revision as of 19:59, 15 November 2011
Line 1:		Line 1:
	Sniper does currently not support the following application behavior:		Sniper does currently not support the following application behavior:
		+
		+	* Spawning more threads than cores. Sniper does not model an OS or scheduler, so each core runs exactly one thread. When threads end, their core becomes free again to run new threads, but at no point in time can there be more threads active than the number of cores specified with the <code>-n</code> command-line parameter.

	* Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)		* Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)

← Older revision	Revision as of 15:20, 5 December 2011
(No difference)