view src/toolcheck @ 26498:e36aefc588c2 v8.2.3779

patch 8.2.3779: using freed memory when defining a user command recursively Commit: https://github.com/vim/vim/commit/205f29c3e9b895dbaa4f738046da455a93c3812a Author: Bram Moolenaar <Bram@vim.org> Date: Fri Dec 10 21:46:09 2021 +0000 patch 8.2.3779: using freed memory when defining a user command recursively Problem: Using freed memory when defining a user command from a user command. Solution: Do not use the command pointer after executing the command. (closes #9318)
author Bram Moolenaar <Bram@vim.org>
date Fri, 10 Dec 2021 23:00:04 +0100
parents 3fc0f57ecb91
children
line wrap: on
line source

#!/bin/sh
# toolcheck -- check for tools that have severe bugs. Good that all the buggy
#	       tools identify by version numbers. This is the spirit of GNU :-)
#
# 24.7.95 jw.

retval=0
reply="`sh -version -c exit 2>&1 < /dev/null`"
case "$reply" in
	GNU*1.14.3*)
		echo "- sh is	'$reply'";
		echo "  CAUTION: This shell has a buggy 'trap' command.";
		echo "           The configure script may fail silently.";
		retval=1;
		;;
	GNU*)
		echo "- sh is	'$reply' - probably OK.";
		;;
	*)	;;
esac

reply="`sed --version 2>&1 < /dev/null`"
case "$reply" in
	GNU\ sed\ version\ 2.0[34])
		echo "- sed is	'$reply'";
		echo "  CAUTION: This sed cannot configure screen properly."
		retval=1;
		;;
	GNU\ sed\ version\ 2.05|GNU\ sed\ version\ 2.03\ kevin)
		echo "- sed is	'$reply' - good.";
		;;
	GNU*)	echo "- sed is	'$reply'.";
		;;
	*)	;;
esac
exit $retval