Skip to content
Snippets Groups Projects
Select Git revision
  • dc80973726d709371d70f4cc85a12c8f18bf2490
  • master default protected
  • android-7.1.2_r28_klist
  • oreo-mr1-iot-release
  • sdk-release
  • pie-cts-dev
  • pie-cts-release
  • pie-vts-release
  • nougat-iot-release
  • pie-gsi
  • pie-platform-release
  • pie-r2-release
  • pie-r2-s1-release
  • pie-release
  • pie-dev
  • oreo-m4-s4-release
  • o-mr1-iot-preview-8
  • oreo-m2-s2-release
  • oreo-m2-s1-release
  • oreo-m6-s2-release
  • oreo-m6-s3-release
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-cts-6.0_r31
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
41 results

AndroidSystemCore

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Greg Hackmann authored
    Both humans and the clang static analyzer find libadf's error handling
    confusing.
    
    Now that the platform has better C++ support, we can clean up things up
    by switching to C++ and using STL + RAII in targeted parts of the code.
    This isn't a complete rewrite in idiomatic C++, but it's enough to get
    rid of all the "goto" statements (and the false-positive memory leaks
    found by clang's static analyzer).
    
    Bug: 27125399
    
    Test: WITH_STATIC_ANALYZER=1 mmm system/core/adf/libadf
    Test: /data/nativetest/adf-unit-tests/adf-unit-tests (on Nexus 9)
    Test: /data/nativetest64/adf-unit-tests/adf-unit-tests (on Nexus 9)
    Change-Id: Ie9dd5d5dc424d1a3ddcc3cba836fce04190f46fd
    Signed-off-by: default avatarGreg Hackmann <ghackmann@google.com>
    dc809737
    History