Forwardtrace of filenames does not contain every child function

Issue Summary

While using the forwardtrace feature, I noticed that it wasn't producing a complete tree of all of the children functions for each captured function. It seemed to be capturing all of the backtraces for each function called from the specified filename, but there were some sibling children that were getting lost in the mix.

So this is just a reminder to dig into this some more since it obviously isn't working 100%.

I was able to still see the full tree without a problem, but just beware that using the forwardtrace feature may not be properly displaying a complete picture of every child -- especially if it's a tree nested with the capture functions.