Somehow mapping mostly works, but somehow breakpoints don't hit.
Reported by
richt...@gmail.com,
Apr 24 2018
|
|||||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: <Linux/Win/Mac> Chrome version: <your chrome version> What are the details of your project? - Source code (if any): http://github.com/example/example I can't publish the source code here. - Build System: gulp/grunt/webpack/rollup/... webpack/typescript/awesome-typescript-loader - HTTP server: node HTTP/nginx/apache... express Assets failed to link (or incorrectly linked): 1. It looks like the assets linked correctly, but every once in a while the system gets into a mode (tried 66 and 68 dev tools) where you can no longer stop at those scripts. 2. The stack trace has this weird "push../src/..." in routine when you do end up stepping into the code (which does work) but you cannot put a breakpoint and stop there. 3. It sounds crazy but I have been struggling with it for quite a while. Some of the code generates exceptions and I can see a red underline where the exception happens but I cannot put a breakpoint on that line and have it stop there. If possible, please attach a screenshot of network sources navigator which should show which resources failed to map Images: Picture of breakpoint that's not being hit. Picture of breakpoint of the calling method which does work. Picture when stepping into the original code by putting a breakpoint further up. This also shows the weird "push..src/" prepend of the stack location I can't figure out where it came from.
,
Apr 24 2018
,
May 28 2018
Adding the label 'TE-NeedsTriageHelp' as the issue seems to be out of TE's scope. Thanks!
,
May 30 2018
,
Sep 25
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by richt...@gmail.com
, Apr 24 2018250 KB
250 KB View Download