On 2025-01-03 SHITAMORI Akira <sit...@gmail.com> wrote:
> https://github.com/arakiken/mlterm/commit/4eb3aa4bba9d918b1923b5a46a67c92142ecaade
> Will this change fix it?

Hello,

I have packaged GIT HEAD and pushed to
https://salsa.debian.org/debian/mlterm/-/tree/tmp-ametzler-2025-snapshot?ref_type=heads

[I have not yet pushed the corresponding changes to
upstream/pristine-tar to not mess up the repo. - I can happily upload
to experimental if Ahmed wants me to.]

It does not crash for me. Valgrind is not totally happy:
testit@argenau:~$ valgrind mlterm
==356486== Memcheck, a memory error detector
==356486== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==356486== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==356486== Command: mlterm
==356486==
==356486== Syscall param writev(vector[0]) points to uninitialised byte(s)
==356486==    at 0x4F392E0: writev (writev.c:26)
==356486==    by 0x534A015: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0)
==356486==    by 0x534A560: xcb_writev (in 
/usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0)
==356486==    by 0x4D26C94: _XSend (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0)
==356486==    by 0x4D270B5: _XFlush (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0)
==356486==    by 0x4D0699D: XFlush (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0)
==356486==    by 0x14E979: ??? (in /usr/bin/mlterm)
==356486==    by 0x118DE4: ??? (in /usr/bin/mlterm)
==356486==    by 0x117D9C: ??? (in /usr/bin/mlterm)
==356486==    by 0x4E52D67: (below main) (libc_start_call_main.h:58)
==356486==  Address 0x55095c4 is 20 bytes inside a block of size 16,384 alloc'd
==356486==    at 0x48489F3: calloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==356486==    by 0x4D15CBA: XOpenDisplay (in 
/usr/lib/x86_64-linux-gnu/libX11.so.6.4.0)
==356486==    by 0x11B6F9: ??? (in /usr/bin/mlterm)
==356486==    by 0x11A5D3: ??? (in /usr/bin/mlterm)
==356486==    by 0x11B34F: ??? (in /usr/bin/mlterm)
==356486==    by 0x118DCC: ??? (in /usr/bin/mlterm)
==356486==    by 0x117D9C: ??? (in /usr/bin/mlterm)
==356486==    by 0x4E52D67: (below main) (libc_start_call_main.h:58)
==356486==
==356486==
==356486== HEAP SUMMARY:
==356486==     in use at exit: 350,009 bytes in 7,630 blocks
==356486==   total heap usage: 24,391 allocs, 16,761 frees, 5,310,822 bytes 
allocated
==356486==
==356486== LEAK SUMMARY:
==356486==    definitely lost: 13,181 bytes in 37 blocks
==356486==    indirectly lost: 249,933 bytes in 6,567 blocks
==356486==      possibly lost: 0 bytes in 0 blocks
==356486==    still reachable: 83,407 bytes in 991 blocks
==356486==         suppressed: 0 bytes in 0 blocks
==356486== Rerun with --leak-check=full to see details of leaked memory
==356486==
==356486== Use --track-origins=yes to see where uninitialised values come from
==356486== For lists of detected and suppressed errors, rerun with: -s
==356486== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)
testit@argenau:~$

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Reply via email to