Cover both reported Chrome anonymous function stacktrace lines

The fix in #290 broke the fix in #238. This PR covers both cases. Not sure if it's the most elegant solution, but it's the best I could do within a limited time frame.
Oops!