Re: Help testing release candidate / mc-4.8.28-rc1

On Sun, Mar 20, 2022 at 01:15:41PM +0100, Yury V. Zaytsev wrote:
>TLDR; I would appreciate if you could please test the following tarball 
>on your systems and report any blocker regressions as compared to the 
>previous 4.8.27 release:
>
i tested master instead:

find.c: In function ‘find_cmd’:
find.c:1837:28: warning: ‘start_dir_len’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  1837 |                 p = name + (size_t) start_dir_len;
       |                            ^~~~~~~~~~~~~~~~~~~~~~
find.c:1897:13: note: ‘start_dir_len’ was declared here
  1897 |     ssize_t start_dir_len;
       |             ^~~~~~~~~~~~~

coord_cache.c: In function ‘mcview_ccache_add_entry’:
coord_cache.c:97:5: warning: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Wdeprecated-declarations]
    97 |     cache->cache[pos] = g_memdup (entry, sizeof (*entry));
       |     ^~~~~
In file included from /usr/include/glib-2.0/glib.h:82,
                  from ../../lib/global.h:66,
                  from coord_cache.c:57:
/usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
   257 | gpointer              g_memdup         (gconstpointer mem,
       |                       ^~~~~~~~

`mc -P $file` doesn't work any more when the file already exists (which 
is of course the case after file=`mktemp`).
_______________________________________________
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel