<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/113399>113399</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            new/delete leaks are caught on return, but can they be caught on throw?
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          AE1020
      </td>
    </tr>
</table>

<pre>
    *(Note: I'm using Ubuntu clang version 18.1.3, but I also pulled and built 20.0.0 to see if things were different, or if there were any new settings.)*

Leaks of unpaired `new` seem to be caught well so long as you are using `return`:

    const char* Leak_IS_Detected_Test(int x) {
        bool* guard = new bool;
 if (x > 0)
            return "This path leaks, and is reported";
 delete guard;
        return "This path has no leak";
 }

> $ clang --analyze caught.cpp
> caught.cpp:4:16: warning: Potential leak of memory pointed to by 'guard' [cplusplus.NewDeleteLeaks]
>    4 |         return "This path leaks, and is reported";

But I would also like to catch `new leaks (and/or `malloc()` leaks) in the cases of throws:

    const char* Leak_NOT_Detected_Test(int x) {
        bool* guard = new bool;
 if (x > 0)
            throw "This path leaks, but doesn't report";
 delete guard;
        return "This path has no leak";
 }

Is there some fiddling of settings such that this could be considered a leak?  I got an AI suggestion to try an alternate path diagnostics mode, but if this was the correct incantation it didn't have any effect:

    clang --analyze -Xanalyzer -analyzer-config -Xanalyzer path-diagnostics-alternate=true not-caught.cpp

For what I am doing, I'm not concerned whether it's a literal throw or a function that calls the throw with an attribute.  But I've gathered that `noreturn` functions are conservatively assumed to possibly be `exit()`s so they do not generate reports.

If throws cannot be checked, are there other attributes besides `noreturn` which would get the same checks as a return statement in terms of control flow?
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJy8VluL4zgT_TXKS5Fgy7k-5CHdmUDgY76FnYV9G2SpYmtHloJUjjv765eSnb7MXlhYGEO7jUqqy6lTR1Ep2cYj7sXqSayOM9VTG-L-8KksZDGrg7nvhTwIuf0cCEV1gLOQmw76ZH0Dv9S9px60U76BG8Zkg4dyuygXlZDPUPcEZ1AuBbj2zqEB5Q3UvXUEslgUiwIoQEIEewFqrW8SDBgRjL1cMKIn9hLiaGZDtip_B48DJCTiMwshd5xjcRTF9P4fqm8JwgV6f1U2ogGxLjwOYl1wvI7j1gha9U1LMKBzkAK44BtQCe6hBxVxKlKsi4jURy_Whag-hAEA0MEnAt2qKOQBOPDX889fj0ioCc3XL5hIyK31BC9C7kBsnt7O8lOH4Phk06toQFTHXFterR5b7QWE3L6AqD5BwdV-8MDPmCEIKb-0NsFVUQuOQWAEGXWbIOI1REIjpHxzbdAh4Rj9bfUfvLYqgQ_Z-QdHYnN8Dw2nKuRy4sZ8rrxy998fkC_09fq2791adViK6lCumWmDit76hj9_CoSerHI5Lje2wy7EO1yD9YQm9_MOQm7GQuQGxOpJX12f-G_xGYdjLjQTQ6yOb8EBYAli8_yfoRzfT5nzQ-idGZnv7Dfk9LQi3U40HP1xT5U3Qp5CZEOnnAtayC13eF08gu7AeqY_aJUwk5raGIb077j4-f9ffjgZc35_AyBrggmYvJAbmnD8IYQ8p0lDUugQLtYYx9MdLq86AqnXLVCriMUogc5NZJkIPlmDLCNqjFOdAM7QBALl4XCG1DcNJmL5owAU77yuHGH0inDM01jV-JDI6gRdMPhAY9S-BINKY5tDjKgJrNfKk8pOLYGxZsSsVbdRA_FyQU1_RYPvZm7-6_QV4bEW5zr4i23e2zjL-bss568FiOpIsUfwgeZ_GuD8ZgoPjNwZVAcm8NzK5-my8IEYQ43Ro4GhRW4EWBJykxhRSxiVm2gTIii49F6PaLJPrZwbsRm3DJbaDDBRtHVPuADIcyfk5obQqNxoMx7miQuvAv7qOWWF585ivCmyN3R3UCn13agm15CSrd2d-y_WBb5wutNkJr4sqMU7mJCLa9Bj5EaPfE6LD8R7DCxo5Xk3M6pF_Y3l4zmnMRIzZFhei0pQI9MufV_C0FrdThLTIGVgkuomr4lvMPWYlESKsENPWUQwdllAdPAUg4OLC4OoTjOzr8yu2qkZ7suN3K2XsirLWbtfl6pSqqpWpdSb3VaWWhfLWumyRLkxej2ze1nIZVnIqijKclUu6t1muV3LujS1RFUVYllgp6xbOHfrFiE2M5tSj_uyrKrdbuZUjS7l3x5SstRkK4_x6jiLez40r_smiWXhbKL05oYsOdzzlS5Pk2SMoprbOt7rwU8wPEZNKz_2rX6_J3eHYeij27dE1yyt8iTkqbHU9vVCh07IE8ee_s2vMfzGwydPOeMk5Gkq6baXfwQAAP__WYD5Rw">