<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:jordan_rose@apple.com" title="Jordan Rose <jordan_rose@apple.com>"> <span class="fn">Jordan Rose</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Memory leak with realloc() not reported."
   href="http://llvm.org/bugs/show_bug.cgi?id=19585">bug 19585</a>
        <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
                
           </td>
           <td>jordan_rose@apple.com
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>WONTFIX
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Memory leak with realloc() not reported."
   href="http://llvm.org/bugs/show_bug.cgi?id=19585#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED WONTFIX - Memory leak with realloc() not reported."
   href="http://llvm.org/bugs/show_bug.cgi?id=19585">bug 19585</a>
              from <span class="vcard"><a class="email" href="mailto:jordan_rose@apple.com" title="Jordan Rose <jordan_rose@apple.com>"> <span class="fn">Jordan Rose</span></a>
</span></b>
        <pre>The MallocChecker tries to strike a balance between people who try to handle
allocation failure and people who don't. Most applications aren't really
equipped to handle malloc or realloc failing -- even if they recover from that
error, they'll crash the next time through the event loop, or similar. So, the
analyzer won't force you to check the result of malloc or realloc, and will
assume success if you don't. If you /do/ check for failure, though, then it can
perform additional checks based on that knowledge, like the realloc leak.

This is something that we could take a configuration option for, but we
currently don't have one.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>