db: return_id was set incorrectly when inline functions were used

db: return_id was set incorrectly when inline functions were used

This is a bad bug.

We would restart counting the return_ids whenever we hit an inline
function.  That meant that the next return would over write some data
from the previous return instead of being recorded in a separate slist and
then merged.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>