Difference between revisions of "Known Issues"

From Sniper
Jump to navigation Jump to search
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)

Revision as of 06:12, 14 December 2011

Unsupported Application Behavior

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 and other synchronous signals (internal bug #121)