Haven’t broken gmic
as I did early this AM. That remains the single failure. Have tried ten or so times now using a generic gmic
and one built through the valgrind
Makefile target. These have all been unexceptional; they fetched their respective update files and installed them in $HOME/.config/gmic
.
The following is a canonical run. gmic
is /usr/bin/gmic
, a v. 3.2.4 that (I think) came from a generic gmic.eu debian binary install package some time ago. ./gmic
(in the local build directory) was built with the valgrind
Makefile target against commit d56391e307de. TLDR; Identical behavior. The warning, per StackOverflow, is not something that an end-user needs to care about: Warning: set address range perms:.
gosgood@Alice ~/gmic/src $ valgrind --leak-check=full gmic update
==2710== Memcheck, a memory error detector
==2710== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==2710== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==2710== Command: gmic update
==2710==
[gmic]-0./ Start G'MIC interpreter.
[gmic]-0./ Update command definition file '/home/gosgood/.config/gmic/update324.gmic' from the G'MIC server.==2710== Warning: set address range perms: large range [0x25328040, 0x35328048) (undefined)
==2710== Warning: set address range perms: large range [0x25328028, 0x35328060) (noaccess)
==2710== Warning: set address range perms: large range [0x4785e040, 0x5785e048) (undefined)
==2710== Warning: set address range perms: large range [0x4785e028, 0x5785e060) (noaccess)
[gmic]-0./ End G'MIC interpreter.
==2710==
==2710== HEAP SUMMARY:
==2710== in use at exit: 122,304 bytes in 1,378 blocks
==2710== total heap usage: 11,933,262 allocs, 11,931,884 frees, 2,281,102,963 bytes allocated
==2710==
==2710== LEAK SUMMARY:
==2710== definitely lost: 0 bytes in 0 blocks
==2710== indirectly lost: 0 bytes in 0 blocks
==2710== possibly lost: 0 bytes in 0 blocks
==2710== still reachable: 122,304 bytes in 1,378 blocks
==2710== suppressed: 0 bytes in 0 blocks
==2710== Reachable blocks (those to which a pointer was found) are not shown.
==2710== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==2710==
==2710== For lists of detected and suppressed errors, rerun with: -s
==2710== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
gosgood@Alice ~/gmic/src $ valgrind --leak-check=full ./gmic update
==2713== Memcheck, a memory error detector
==2713== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==2713== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==2713== Command: ./gmic update
==2713==
[gmic]./ Start G'MIC interpreter (v.3.3.6).
[gmic]./ Update command definition file '/home/gosgood/.config/gmic/update336.gmic' from the G'MIC server.==2713== Warning: set address range perms: large range [0x25bbd040, 0x35bbd048) (undefined)
==2713== Warning: set address range perms: large range [0x25bbd028, 0x35bbd060) (noaccess)
==2713== Warning: set address range perms: large range [0x59c8e040, 0x69c8e048) (undefined)
==2713== Warning: set address range perms: large range [0x59c8e028, 0x69c8e060) (noaccess)
[gmic]./ End G'MIC interpreter.
==2713==
==2713== HEAP SUMMARY:
==2713== in use at exit: 122,304 bytes in 1,378 blocks
==2713== total heap usage: 12,704,383 allocs, 12,703,005 frees, 2,546,625,336 bytes allocated
==2713==
==2713== LEAK SUMMARY:
==2713== definitely lost: 0 bytes in 0 blocks
==2713== indirectly lost: 0 bytes in 0 blocks
==2713== possibly lost: 0 bytes in 0 blocks
==2713== still reachable: 122,304 bytes in 1,378 blocks
==2713== suppressed: 0 bytes in 0 blocks
==2713== Reachable blocks (those to which a pointer was found) are not shown.
==2713== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==2713==
==2713== For lists of detected and suppressed errors, rerun with: -s
==2713== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
So, whistling a little tune… ![:kissing: :kissing:](https://discuss.pixls.us/images/emoji/apple/kissing.png?v=12)