Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incorrect stack trace on Windows #4

Closed
thaiat opened this issue Jun 9, 2014 · 4 comments
Closed

Incorrect stack trace on Windows #4

thaiat opened this issue Jun 9, 2014 · 4 comments
Labels
bug

Comments

@thaiat
Copy link
Contributor

thaiat commented Jun 9, 2014

Hi,
Whenever there is an exception in a test or source code, karma reports the error as coming from the .browserify file, which makes it difficult to locate it. Note that i'm running browserify with the debug mode set to true and karma with PhantomJS.
Is there anyway to get the original error location ?
@nikku
Copy link
Owner

nikku commented Jun 9, 2014

I thought lib/bro.js#L244 was doing it, but as it looks like the feature is currently broken.

Must look into it and inspect the actual pulled out source-map contents.

@nikku
Copy link
Owner

nikku commented Jun 10, 2014

I presume you are using Windows? If so, this is due to karma-runner/karma#1097.

@thaiat
Copy link
Contributor Author

thaiat commented Jun 10, 2014

nicely spotted!!!!

@nikku nikku changed the title Incorrect stack trace Incorrect stack trace on Windows Jun 10, 2014
@nikku nikku added the bug label Jun 10, 2014
@nikku
Copy link
Owner

nikku commented Jun 26, 2014

Closing this as it is a Karma runner issue.

@nikku nikku closed this as completed Jun 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nikku @thaiat