Skip to content
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.

TraceKit.computeStackTrace evaluates error to {} #68

Open
Myztiq opened this issue Jan 30, 2015 · 1 comment
Open

TraceKit.computeStackTrace evaluates error to {} #68

Myztiq opened this issue Jan 30, 2015 · 1 comment

Comments

@Myztiq
Copy link

Myztiq commented Jan 30, 2015

I have created a reproduction hosted here: http://raven-undefined.divshot.io/
With source here: https://github.com/Myztiq/raven-undefined

A request to an invalid file triggers an error with the message Unexpected token < and when TraceKit.computeStackTrace is done it results in {} being spat out. When used in conjunction with Raven this results in sentry getting errors with undefined as the value and message.

@Myztiq Myztiq changed the title TraceKit.computeStackTrace evaluates error to {}` TraceKit.computeStackTrace evaluates error to {} Jan 30, 2015
@niemyjski
Copy link
Collaborator

@Myztiq , I'm helping manage the TraceKit project. Can you please create a pull request for this here https://github.com/csnover/TraceKit so we can get it merged in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants