r271544 - [docs] Add a limitations section to SourceBasedCodeCoverage.rst

[Vedant Kumar via cfe-commits]

Author: vedantk
Date: Thu Jun  2 12:19:45 2016
New Revision: 271544

URL: http://llvm.org/viewvc/llvm-project?rev=271544&view=rev
Log:
[docs] Add a limitations section to SourceBasedCodeCoverage.rst

Modified:
    cfe/trunk/docs/SourceBasedCodeCoverage.rst

Modified: cfe/trunk/docs/SourceBasedCodeCoverage.rst
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/SourceBasedCodeCoverage.rst?rev=271544&r1=271543&r2=271544&view=diff
==============================================================================
--- cfe/trunk/docs/SourceBasedCodeCoverage.rst (original)
+++ cfe/trunk/docs/SourceBasedCodeCoverage.rst Thu Jun  2 12:19:45 2016
@@ -165,9 +165,9 @@ A few final notes:
   indexed profiles. To combine profiling data from multiple runs of a program,
   try e.g:
 
-.. code-block:: console
+  .. code-block:: console
 
-    % llvm-profdata merge -sparse foo1.profraw foo2.profdata -o foo3.profdata
+      % llvm-profdata merge -sparse foo1.profraw foo2.profdata -o foo3.profdata
 
 Format compatibility guarantees
 ===============================
@@ -184,3 +184,20 @@ Format compatibility guarantees
 * There is a third format in play: the format of the coverage mappings emitted
   into instrumented binaries. Tools must retain **backwards** compatibility
   with these formats. These formats are not forwards-compatible.
+
+Drawbacks and limitations
+=========================
+
+* Code coverage does not handle stack unwinding in the presence of uncaught
+  exceptions precisely. Consider the following function:
+
+  .. code-block:: cpp
+
+      int f() {
+        may_throw();
+        return 0;
+      }
+
+  If the function ``may_throw()`` propagates an exception into ``f``, the code
+  coverage tool may mark the ``return`` statement as executed even though it is
+  not.