On 01/25/2015 02:23 PM, scan-admin@coverity.com wrote:
*** CID 1266445:  Explicit null dereferenced  (FORWARD_NULL)
/cppuhelper/source/component_context.cxx: 747 in cppu::ComponentContext::disposing()()
741             &envs, &envCount, &rtl_allocateMemory, OUString("java").pData);
742         assert(envCount >= 0);
743         assert(envCount == 0 || envs != nullptr);
744         for (sal_Int32 i = 0; i != envCount; ++i) {
745             assert(envs[i] != nullptr);
746             assert(envs[i]->dispose != nullptr);
     CID 1266445:  Explicit null dereferenced  (FORWARD_NULL)
     Dereferencing null pointer "envs".
747             (*envs[i]->dispose)(envs[i]);
What was the state of these builds again, they're implicitly 
--disable-debug, --disable-assert-always-abort, and making them 
--enable-debug would run out of resources?  Could they be made 
--enable-assert-always-abort, in the hope that that would silence the 
above false positive (or would that need some explicit coverity comment 
annotation anyway)?
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.