As shown in the picture, the evhttp_write_cb with function entry address "0x100000" is passed as an argument for external function call bufferevent_setcb. However, the decompiled code shows the function as a number "0x100000" instead of function name.
Once the entry address of evhttp_write_cb changed, the argument shows correctly as below:
Since the p-code interface correctly shows the function name, I personally think (have not checked, and may be wrong) this is because of some implementation error among the boundary examination, probably related to the "addrforce" in varnode.hh or printing system like (printc.cc).
As shown in the picture, the
evhttp_write_cb
with function entry address "0x100000" is passed as an argument for external function callbufferevent_setcb
. However, the decompiled code shows the function as a number "0x100000" instead of function name. Once the entry address ofevhttp_write_cb
changed, the argument shows correctly as below: Since the p-code interface correctly shows the function name, I personally think (have not checked, and may be wrong) this is because of some implementation error among the boundary examination, probably related to the "addrforce" in varnode.hh or printing system like (printc.cc).