The report is a bit unclear on what, exactly, you asked cscope to do, and what you were using to look at its output. Which -L mode client was that, and why woud its potential failure to cope with tab characters, which are perfectly fine in C source code, have to be seen as cscope's problem? The way the output was mangled by SF's markdown processing also makes it quite hard to judge what might be wrong here. I'm pretty sure there were not two <unknown> tags in cscope's actual output. It also doesn't...
The report is a bit unclear on what, exactly, you asked cscope to do, and what you were using to look at its output. Which -L mode client was that, and why woud its potential failure to cope with tab characters, which are perfectly fine in C source code, have to be seen as cscope's problem? The way the output was mangled by SF's markdown processing, making also makes it quite hard to judge what might be wrong here. I'm pretty sure there were not two <unknown> tags in cscope's actual output. It also...
Hmmm... checked out git current source straight from their original upstream. Class 1: No two-line function definition for radius_das_disconnect matching your description seems to exist in there. The definition has looked like this, for the last 14 years and counting: static struct radius_msg * radius_das_disconnect(struct radius_das_data *das, struct radius_msg *msg, const char *abuf, int from_port) What gives? The issue itself does exist, and is most likely an instance of the well-known and documented...
noautititle, notitle and empty title
The primary issue here is that this third-party tool is trying way too hard. It uses multiplot mode for no discernible reason, and it uses enormous amounts of tricks and manual overrides to achive what gnuplot itself would have done by itself, if left to its own devices. E.g. instead of manually inserting 4 key entries, and then telling gnuplot not to generate any of its own, it would have been way simpler to just add title 'Cholesky'etc. direktly to the plot command.
See "help set print"
Spurious bells when using mappings from cscope_maps.vim
Hmmm... that's very strange. That file has not been modified at all for 21 years. I find it extremely surprising that nobody would have ever noticed this in all that time. But then again, most people would have turned off the bell in their terminal emulators long ago, I think. :-) But for now I'll have to take your word for it. A modified version is now on the page.