Difference between revisions of "Known Issues"

From Sniper
Jump to navigation Jump to search
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.
+
* 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), use of signals (internal bug #121)

Revision as of 19:59, 15 November 2011

Sniper does currently not support the following application behavior:

  • 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 -n command-line parameter.
  • Instruction exceptions (such as SIGFPE, SIGSEGV), use of signals (internal bug #121)