Mercurial > vim
view src/toolcheck @ 14147:de75c249723d v8.1.0091
patch 8.1.0091: MS-Windows: Cannot interrupt gdb when program is running
commit https://github.com/vim/vim/commit/4551c0a9fcdbdef52836d4852686d54b5e47fdaf
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Jun 20 22:38:21 2018 +0200
patch 8.1.0091: MS-Windows: Cannot interrupt gdb when program is running
Problem: MS-Windows: Cannot interrupt gdb when program is running.
Solution: Add debugbreak() and use it in the terminal debugger.
Respect 'modified' in a prompt buffer.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Wed, 20 Jun 2018 22:45:05 +0200 |
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