Skip to content

صدای خلصه #125

@Ramin078

Description

@Ramin078

here the valgrind output on the arm64 porter box from debian


(sid_arm64-dchroot)picca@amdahl:~/hkl/Documentation/figures$ ../../libtool --mode=execute valgrind  --leak-check=full --show-leak-kinds=all --main-stacksize=1000000 sirius

==7368== Memcheck, a memory error detector

==7368== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.

==7368== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info

==7368== Command: /home/picca/hkl/Documentation/figures/.libs/sirius

==7368==

==7368== Invalid write of size 8

==7368==    at 0x1430D8: generator_new_ (generator.c:38)

==7368==    by 0x144B77: trajectory_gen (hkl2.c:246)

==7368==    by 0x144C2B: Trajectory_solve (hkl2.c:288)

==7368==    by 0x11D323: main (sirius.c:161)

==7368==  Address 0x23c0 is not stack'd, malloc'd or (recently) free'd

==7368==

==7368==

==7368== Process terminating with default action of signal 11 (SIGSEGV)

==7368==  Access not within mapped region at address 0x23C0

==7368==    at 0x1430D8: generator_new_ (generator.c:38)

==7368==    by 0x144B77: trajectory_gen (hkl2.c:246)

==7368==    by 0x144C2B: Trajectory_solve (hkl2.c:288)

==7368==    by 0x11D323: main (sirius.c:161)

==7368==  If you believe this happened as a result of a stack

==7368==  overflow in your program's main thread (unlikely but

==7368==  possible), you can try to increase the size of the

==7368==  main thread stack using the --main-stacksize= flag.

==7368==  The main thread stack size used in this run was 1048576.

==7368==

==7368== HEAP SUMMARY:

==7368==     in use at exit: 45,052 bytes in 234 blocks

==7368==   total heap usage: 278 allocs, 44 frees, 52,804 bytes allocated

==7368==

==7368== 64 bytes in 4 blocks are possibly lost in loss record 1 of 8

==7368==    at 0x4844BBC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 184 bytes in 1 blocks are possibly lost in loss record 2 of 8

==7368==    at 0x4846EE8: realloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 688 bytes in 45 blocks are still reachable in loss record 3 of 8

==7368==    at 0x4844BBC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 1,104 bytes in 13 blocks are possibly lost in loss record 4 of 8

==7368==    at 0x4846CDC: calloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 4,096 bytes in 1 blocks are still reachable in loss record 5 of 8

==7368==    at 0x4846EE8: realloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 8,192 bytes in 1 blocks are definitely lost in loss record 6 of 8

==7368==    at 0x4844C84: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 12,976 bytes in 138 blocks are still reachable in loss record 7 of 8

==7368==    at 0x4846CDC: calloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== 17,748 bytes in 31 blocks are still reachable in loss record 8 of 8

==7368==    at 0x4844C84: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)

==7368==

==7368== LEAK SUMMARY:

==7368==    definitely lost: 8,192 bytes in 1 blocks

==7368==    indirectly lost: 0 bytes in 0 blocks

==7368==      possibly lost: 1,352 bytes in 18 blocks

==7368==    still reachable: 35,508 bytes in 215 blocks

==7368==                       of which reachable via heuristic:

==7368==                         newarray           : 1,536 bytes in 16 blocks

==7368==         suppressed: 0 bytes in 0 blocks

==7368==

==7368== For counts of detected and suppressed errors, rerun with: -v

==7368== ERROR SUMMARY: 5 errors from 5 contexts (suppressed: 0 from 0)

Segmentation fault

Originally posted by @picca in #65

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions