On Thu, 2009-07-16 at 12:31 -0700, Roland McGrath wrote:
IMHO in dwfl_addrmodule I expect "just no match" to be a
situation, because you'd pass some random address to it to find out if it's
a code address vs a heap/stack/etc address. If there is some error in the
DWARF, you want to barf with whatever dwfl_errmsg says. If it is just a
heap/stack/etc address, you want to just know that there was no match.
OK, that does make sense. It is just not how we (systemtap) use it at
the moment, in most cases we unconditionally call dwfl_errmsg(-1) to
generate an error string when a dwfl call fails. Will need to update
that a bit then to first check the error code explicitly to distinquish
"failure" from "error".