Problems identifying file with errors in Chrome dev tools

Asked

Viewed 39 times

0

I have an aspx page, which by Chrome dev tools gives me the following error:

Uncaught Syntaxerror: Unexpected token ILLEGAL

The problem he points to that line:

prs0101.aspx.561

It turns out that this file does not have the 561 line. Then I understood that this error may be giving in some included javascript file. Well, at the time of the error, in the SOURCE tab, it opens two more environments, the first containing three tabs: SOURCE, CONTENT Scripts and SNIPPETS. And the other tab called Resource script. Well, it comes blank, when I click on the SOURCE TAB and then on the SOURCE(Internal) TAB, it opens some folders and one where the error seems to be. I click and open js Ajaxtoolkit and go to page 561 and find a comment. I still can’t understand where the error really is, it’s not clear. In IE it’s even worse. How do I get to the bug using dev tools? I don’t know if I’m clear. Available.

  • As far as I know when it comes to Chrome the page is already compiled ... already has a lot of information together. It would be interesting to debug directly in the visual studio

  • It would be interesting if you had a link to application.

  • @Otto, yes I do, and that’s what I’m doing.

  • @pnet some evolution with debug ?

  • @Otto, so my environment is bugged, but I’m debugging it by the c# and taking out the problems that come along. I just posted a difficulty, called javascript, coming from debug. It is evolving yes.

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.