Looking up a tag that occurs multiple times in the ctags database (e.g. a function definition and a prototype) sometimes results in only the first (or a first few) occurrence being returned, but not all. 

The problem happens randomly and is not straightforward to reproduce. It is an invalid pointer dereference in kate/plugins/kate-ctags/tags.cpp. See additional information below.

Due to the nature of the bug, it could potentially cause kate to crash, but I've not been able to trigger this so far.

Reproducible: Sometimes

Steps to Reproduce:
1. Enable kate-ctags plugin
2. Create a ctags database that contains multiple instances of the same tag (preferably, 6-7)
3. Point kate-ctags to that database
4. Try to lookup the tag - try several prefixes of varying lengths
Actual Results:  
Sometimes, only the first tag from the ctags index gets returned. Sometimes, more than one, but not all.

Expected Results:  
All tags from the index should be returned.

The problem is in kate/plugins/kate-ctags/tags.cpp, methods Tags::numberOfMatches() and Tags::getMatches(), in the following bit of code (abbreviated for clarity):

	if ( ctags::tagsFind( file, &entry, tagpart.toLocal8Bit(), ...
	{
		do
		{
			...
		}
		while ( ctags::tagsFindNext( file, &entry ) == ctags::TagSuccess );
	}

tagpart.toLocal8Bit() creates a temporary QByteArray object, which is converted to const char * and passed to ctags::tagsFind. However, ctags::tagsFind internally stores this pointer inside the tagFile structure, for later re-use by findNext. But, by the time findNext is called, this temporary is destroyed and the pointer is no longer valid, so findNext randomly fails.

This QByteArray should really be pulled out of the function call, like so:

	QByteArray name = tagpart.toLocal8Bit();
	if ( ctags::tagsFind( file, &entry, name, ...
	{

which solves the problem. I can provide a (tested) patch, if necessary.