Attachment 120097 Details for Bug 93091 – output of "valgrind clinfo"

output of "valgrind clinfo"

valgrind.clinfo.txt (text/plain), 3.44 KB, created by Aaron Watry on 2015-11-24 22:33:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Aaron Watry

Created: 2015-11-24 22:33:23 UTC

Size: 3.44 KB

patch

obsolete

>==30887== Memcheck, a memory error detector
>==30887== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
>==30887== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
>==30887== Command: clinfo
>==30887== 
>==30887== Invalid read of size 8
>==30887==    at 0x5A3D860: pipe_loader_create_screen (pipe_loader.c:79)
>==30887==    by 0x5AA35D6: clover::device::device(clover::platform&, pipe_loader_device*) (device.cpp:44)
>==30887==    by 0x5ACC485: clover::intrusive_ref<clover::device> clover::create<clover::device, clover::platform&, pipe_loader_device*&>(clover::platform&, pipe_loader_device*&) (pointer.hpp:230)
>==30887==    by 0x5ACBFB6: clover::platform::platform() (platform.cpp:35)
>==30887==    by 0x5A73883: __static_initialization_and_destruction_0(int, int) (platform.cpp:29)
>==30887==    by 0x5A738B3: _GLOBAL__sub_I_platform.cpp (platform.cpp:120)
>==30887==    by 0x40105B9: call_init.part.0 (dl-init.c:72)
>==30887==    by 0x40106CA: call_init (dl-init.c:30)
>==30887==    by 0x40106CA: _dl_init (dl-init.c:120)
>==30887==    by 0x4015586: dl_open_worker (dl-open.c:579)
>==30887==    by 0x4010463: _dl_catch_error (dl-error.c:187)
>==30887==    by 0x40149A2: _dl_open (dl-open.c:663)
>==30887==    by 0x541FFC8: dlopen_doit (dlopen.c:66)
>==30887==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
>==30887== 
>==30887== 
>==30887== Process terminating with default action of signal 11 (SIGSEGV)
>==30887==  Access not within mapped region at address 0x18
>==30887==    at 0x5A3D860: pipe_loader_create_screen (pipe_loader.c:79)
>==30887==    by 0x5AA35D6: clover::device::device(clover::platform&, pipe_loader_device*) (device.cpp:44)
>==30887==    by 0x5ACC485: clover::intrusive_ref<clover::device> clover::create<clover::device, clover::platform&, pipe_loader_device*&>(clover::platform&, pipe_loader_device*&) (pointer.hpp:230)
>==30887==    by 0x5ACBFB6: clover::platform::platform() (platform.cpp:35)
>==30887==    by 0x5A73883: __static_initialization_and_destruction_0(int, int) (platform.cpp:29)
>==30887==    by 0x5A738B3: _GLOBAL__sub_I_platform.cpp (platform.cpp:120)
>==30887==    by 0x40105B9: call_init.part.0 (dl-init.c:72)
>==30887==    by 0x40106CA: call_init (dl-init.c:30)
>==30887==    by 0x40106CA: _dl_init (dl-init.c:120)
>==30887==    by 0x4015586: dl_open_worker (dl-open.c:579)
>==30887==    by 0x4010463: _dl_catch_error (dl-error.c:187)
>==30887==    by 0x40149A2: _dl_open (dl-open.c:663)
>==30887==    by 0x541FFC8: dlopen_doit (dlopen.c:66)
>==30887==  If you believe this happened as a result of a stack
>==30887==  overflow in your program's main thread (unlikely but
>==30887==  possible), you can try to increase the size of the
>==30887==  main thread stack using the --main-stacksize= flag.
>==30887==  The main thread stack size used in this run was 8388608.
>==30887== 
>==30887== HEAP SUMMARY:
>==30887==     in use at exit: 653,830 bytes in 1,131 blocks
>==30887==   total heap usage: 1,722 allocs, 591 frees, 940,347 bytes allocated
>==30887== 
>==30887== LEAK SUMMARY:
>==30887==    definitely lost: 0 bytes in 0 blocks
>==30887==    indirectly lost: 0 bytes in 0 blocks
>==30887==      possibly lost: 7,476 bytes in 117 blocks
>==30887==    still reachable: 646,354 bytes in 1,014 blocks
>==30887==         suppressed: 0 bytes in 0 blocks
>==30887== Rerun with --leak-check=full to see details of leaked memory
>==30887== 
>==30887== For counts of detected and suppressed errors, rerun with: -v
>==30887== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Actions: View

Attachments on bug 93091: 120097 | 120098 | 120146

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.