I discovered this flaw when trying to use the fully-resolved name for a function
probe:

$ stap -l 'kernel.function("send_sigqueue")'
kernel.function("send_sigqueue@kernel/signal.c:1309")
$ stap -l 'kernel.function("send_sigqueue@kernel/signal.c:1309")' --vp 03
[...]
focused on module 'kernel'
selected source file 'arch/x86/kernel/signal.c'
semantic error: libdw failure (dwarf_getsrc_file): no matching address range
semantic error: no match while resolving probe point
kernel.function("send_sigqueue@kernel/signal.c:1309")

It matched arch/x86/kernel/signal.c because we implicitly use a '*/' in front of
source paths.  The arch file is less than 1309 lines long though, so there can't
be any functions there.

However, instead of aborting, we should continue looking at other source files
so we can find the correct function in the plain 'kernel/signal.c'.