debugging errors in user sessions

[Brian Craft]

Is there any solution for finding the location of an error reported by a user after the source has been uglified? I suspect source maps don't help here, because we don't have the browser context to work with. We just have the error, something like 

Object doesn't support this property or method

at line 15

where line 15 includes a dozen modules due to uglification.