Attachment 581476 Details for Bug 809111 – output from valgrind

output from valgrind

probe.log (text/plain), 2.15 KB, created by Samuel Sieb on 2012-05-01 20:55:11 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Samuel Sieb

Created: 2012-05-01 20:55:11 UTC

Size: 2.15 KB

patch

obsolete

>==18142== Memcheck, a memory error detector
>==18142== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
>==18142== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
>==18142== Command: grub2-probe --device /dev/md0 --target=fs
>==18142== Parent PID: 18078
>==18142== 
>==18142== Stack overflow in thread 1: can't grow stack to 0xbe176ff0
>==18142== 
>==18142== Process terminating with default action of signal 11 (SIGSEGV)
>==18142==  Access not within mapped region at address 0xBE176FF0
>==18142==    at 0x80D8E20: grub_disk_cache_fetch (disk.c:112)
>==18142==  If you believe this happened as a result of a stack
>==18142==  overflow in your program's main thread (unlikely but
>==18142==  possible), you can try to increase the size of the
>==18142==  main thread stack using the --main-stacksize= flag.
>==18142==  The main thread stack size used in this run was 8388608.
>==18142== Stack overflow in thread 1: can't grow stack to 0xbe176fdc
>==18142== 
>==18142== Process terminating with default action of signal 11 (SIGSEGV)
>==18142==  Access not within mapped region at address 0xBE176FDC
>==18142==    at 0x4023510: _vgnU_freeres (vg_preloaded.c:58)
>==18142==  If you believe this happened as a result of a stack
>==18142==  overflow in your program's main thread (unlikely but
>==18142==  possible), you can try to increase the size of the
>==18142==  main thread stack using the --main-stacksize= flag.
>==18142==  The main thread stack size used in this run was 8388608.
>==18142== 
>==18142== HEAP SUMMARY:
>==18142==     in use at exit: 1,734,397 bytes in 58,253 blocks
>==18142==   total heap usage: 814,645 allocs, 756,392 frees, 5,822,950,913 bytes allocated
>==18142== 
>==18142== LEAK SUMMARY:
>==18142==    definitely lost: 0 bytes in 0 blocks
>==18142==    indirectly lost: 0 bytes in 0 blocks
>==18142==      possibly lost: 0 bytes in 0 blocks
>==18142==    still reachable: 1,734,397 bytes in 58,253 blocks
>==18142==         suppressed: 0 bytes in 0 blocks
>==18142== Rerun with --leak-check=full to see details of leaked memory
>==18142== 
>==18142== For counts of detected and suppressed errors, rerun with: -v
>==18142== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Actions: View

Attachments on bug 809111: 581451 | 581476 | 581479 | 581487 | 581488 | 581489