This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 268932 - No stacktrace in the output window after debug file and it fails
Summary: No stacktrace in the output window after debug file and it fails
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.2
Hardware: PC Other
: P3 normal (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-10 16:14 UTC by Christian Lenz
Modified: 2016-11-10 16:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
WebStorm JS Stacktrace (30.68 KB, image/png)
2016-11-10 16:14 UTC, Christian Lenz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Lenz 2016-11-10 16:14:23 UTC 
Created attachment 162869 [details]
WebStorm JS Stacktrace

I have a testfile and I wanted to debug it so I did a right click and choose Debug file. After some seconds, I got this error:

debug:
shopSettingsAPI.spec.js:7 ReferenceError: "describe" is not defined
C:\Users\chrl\AppData\Local\NetBeans\Cache\8.2\executor-snippets\debug.xml:83: Java returned: 102
BUILD FAILED (total time: 2 seconds)

of course I'm inside the file and I know why this happens. If I do the same in WebStorm I got really more information. First I see the output, what happens there (Call node with params and the file, like for the maven support in NetBeans) and I got the filename:linenumber which is clickable to jump to the failed part of the source and I got a stacktrace. See the image for what I mean. So I expect a similiar output to be consistent with for example maven in NetBeans etc. pp.


Regards

Chris