Avoid assertion error for statement probe

[Frank Ch. Eigler]

Wenji Huang <wenji.huang@oracle.com> writes:

> Current stap will reach assertion error when no matched function
> is found in source file. For example,
>
> $ stap -e 'probe process("./stap").statement("foo@main.cxx:*") {}'
> stap: dwflpp.cxx:1276: void dwflpp::function_line(int*): Assertion
> `function' failed.
> Aborted

Wow, I thought this was gone.

> I think it's better to give explicit description if no matched
> function is resolved in CU. Like,
>
> $ stap -e 'probe process("./stap").statement("foo@main.cxx:*") {}'
> semantic error: no matched function 'foo' in main.cxx
> semantic error: no probes found

Not a bad idea, but perhaps we don't need that particular "no matched
function" message that covers just this case, considering that the "no
probes found" message can/should be paired with the probe point.


- FChE