view runtime/tools/efm_filter.txt @ 17308:d04de6c49f59 v8.1.1653

patch 8.1.1653: ubsan warns for possibly passing NULL pointer commit https://github.com/vim/vim/commit/0d07155c8bbaca1a527b79da358438253a60839f Author: Bram Moolenaar <Bram@vim.org> Date: Mon Jul 8 22:04:03 2019 +0200 patch 8.1.1653: ubsan warns for possibly passing NULL pointer Problem: Ubsan warns for possibly passing NULL pointer. Solution: Skip code when length is zero. (Dominique Pelle, closes https://github.com/vim/vim/issues/4631)
author Bram Moolenaar <Bram@vim.org>
date Mon, 08 Jul 2019 22:15:04 +0200
parents 3fc0f57ecb91
children
line wrap: on
line source

[adopted from a message that Ives posted in the Vim mailing list]

Some compilers produce an error message that cannot be handled with
'errorformat' in Vim.  Following is an example of a Perl script that
translates one error message into something that Vim understands.


The compiler that generates this kind of error messages (4 lines):

"/tmp_mnt/cm/src/apertos/MoU/MetaCore/MetaCore/common/src/MetaCoreImp_M.cc",
line 50: error(3114):
	   identifier "PRIMITIVE_M" is undefined
	 return(ExecuteCore(PRIMITIVE_M,

You can find a small perl program at the end.
The way I use it is:

:set   errorformat=%f>%l:%c:%t:%n:%m
:set   makeprg=clearmake\ -C\ gnu
:set   shellpipe=2>&1\|\ vimccparse

If somebody thinks this is useful: feel free to do whatever you can think
of with this code.

-Ives
____________________________________________________________
Ives Aerts (SW Developer)	    Sony Telecom Europe
ives@sonytel.be			    St.Stevens Woluwestr. 55
`Death could create most things,    B-1130 Brussels, Belgium
 except for plumbing.'		    PHONE : +32 2 724 19 67
	 (Soul Music - T.Pratchett) FAX   : +32 2 726 26 86