Setting up a break point in a file sets breakpoint in a different file

397 views
Skip to first unread message

inia...@gmail.com

unread,
Jan 25, 2014, 9:07:13 PM1/25/14
to google-chrome-...@googlegroups.com
Steps to reproduce the problem

2. Open the file called dm1--.js in Sources tab
3. Pretty print it
4. Try setting a break point anywhere on this file. Setting a break point at a particular line does not stop execution at that point. Execution stops at a totally different file at some different line. 

This is a bug with the dev tools, right?

Pavel Feldman

unread,
Jan 28, 2014, 10:30:35 AM1/28/14
to Google Chrome Developer Tools
Sounds like a bug. Could you please report it at http://crbug.com/new and prefix title with "DevTools:"?

Regards
Pavel


--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/85e59ef6-f625-4515-8ec2-e82338442b9d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Vsevolod Vlasov

unread,
Jan 28, 2014, 2:42:14 PM1/28/14
to Google Chrome Developer Tools
This is not a bug.

As you can see on the last line of the file, this file has a sourceMappingURL directive.
Because of that DevTools loads sources and maps your breakpoints there.
You could either debug the sources instead of the original file (this is the best option in most of the cases) or disable source maps in DevTools settings.


On Sun, Jan 26, 2014 at 6:07 AM, <inia...@gmail.com> wrote:

--

inia...@gmail.com

unread,
Feb 1, 2014, 5:49:57 AM2/1/14
to google-chrome-...@googlegroups.com
I realised it might have something to do with sourcemaps. Thats why I wanted to confirm before posting it as a bug.
Thanks :)


On Wednesday, 29 January 2014 03:42:14 UTC+8, Vsevolod Vlasov wrote:
This is not a bug.

As you can see on the last line of the file, this file has a sourceMappingURL directive.
Because of that DevTools loads sources and maps your breakpoints there.
You could either debug the sources instead of the original file (this is the best option in most of the cases) or disable source maps in DevTools settings.
On Sun, Jan 26, 2014 at 6:07 AM, <inia...@gmail.com> wrote:
Steps to reproduce the problem

2. Open the file called dm1--.js in Sources tab
3. Pretty print it
4. Try setting a break point anywhere on this file. Setting a break point at a particular line does not stop execution at that point. Execution stops at a totally different file at some different line. 

This is a bug with the dev tools, right?

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages