Developer Tools - Breakpoints not working

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Using cefClient, open the developer tools through tests->Show Developer Tools
2. Browse to a website and add a breakpoint in a javascript file that you know 
will get hit (or html)
3. Perform the action on the website.

What is the expected output? What do you see instead?
The breakpoint doesn't get hit at all. The program just continues to run.

What version of the product are you using? On what operating system?
cef_binary_r195_VS2008 on Windows XP SP3

Please provide any additional information below.

If I use the developer tools from within the Google Chrome browser and run the 
exact same test, breakpoints get hit every time. Just doesn't seem to work 
within CEF.

Original issue reported on code.google.com by rwstoneb...@gmail.com on 23 Mar 2011 at 2:58

[GoogleCodeExporter]

Do breakpoints work in the Chromium test_shell application?

Original comment by magreenb...@gmail.com on 23 Mar 2011 at 3:04

[GoogleCodeExporter]

Is there any other way of getting the Chromium test_shell application without 
downloading and building the entire Chromium source?

Original comment by rwstoneb...@gmail.com on 23 Mar 2011 at 3:33

[GoogleCodeExporter]

You can download the lastest build snapshots here:
http://build.chromium.org/f/chromium/snapshots/chromium-rel-xp/

Original comment by magreenb...@gmail.com on 23 Mar 2011 at 3:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

an additional note: I can see the breakpoint "try" to get hit in CEF. The blue 
breakpoint has a red arrow go over it for a split second, but it doesn't 
actually pause anything.

Original comment by rwstoneb...@gmail.com on 24 Mar 2011 at 7:06

[GoogleCodeExporter]

The Chromium developer's page has build instructions: 
http://dev.chromium.org/developers

The "test_shell" target is part of the chrome.sln solution.

Original comment by magreenb...@gmail.com on 24 Mar 2011 at 7:13

[GoogleCodeExporter]

I try building the test_shell project in the chrome solution and I get a bunch 
of errors (from syntax errors to "a tool returned an error code" 
errors...Unfortunately I don't have the time or resources to throw at trying 
this out in the test_shell application right now.

Is there any other way of debugging this issue?

Another interesting thing to note is that the "Pause" button in the debugger 
tools (in CEF) just says "Pausing" after I press it, but never actually pausing 
anything.

Original comment by rwstoneb...@gmail.com on 25 Mar 2011 at 4:37

[GoogleCodeExporter]

The code in question lives within CEF's browser_devtools_* files. The easiest 
way to understand what isn't working is usually to compare against something 
that is working correctly (in debug mode). If it isn't working in test_shell 
then you can potentially punt the issue by filing a bug with the Chromium 
developers. If you can't build the test_shell application then you probably 
won't succeed in building the Chromium application either. So your remaining 
option is to read the code, run the debugger with CEF and hope you can figure 
it out without having a working (debuggable) basis of comparison.

Original comment by magreenb...@gmail.com on 25 Mar 2011 at 4:47

[GoogleCodeExporter]

now that you mention brower_devtools...in my debug.log file, it has an error 
message: 

[0325/130347:ERROR:browser_devtools_client.cc(63)] NOT IMPLEMENTED

Original comment by rwstoneb...@gmail.com on 25 Mar 2011 at 5:05

[GoogleCodeExporter]

It appears that WebKit inspector breakpoints work in debug builds but not 
release builds. I executed the following test using a debug build at revision 
209:

1. Load the "XMLHttpRequest" test.
2. Launch the inspector and set a breakpoint in the execXMLHttpRequest() 
JavaScript function.
3. Click the button.
4. The breakpoint is hit and you can step through the code.

The release build of revision 181 failed to stop at the breakpoint as you 
describe, and the debug build of revision 181 stopped at the breakpoint and 
then crashed.

Original comment by magreenb...@gmail.com on 25 Mar 2011 at 5:41

• Changed state: Accepted

[GoogleCodeExporter]

That should say revision 195 instead of 181.

Original comment by magreenb...@gmail.com on 25 Mar 2011 at 5:42

[GoogleCodeExporter]

yes, I am seeing the same behavior with the debug build of 195. Any idea when 
an updated Binary Distribution might be due up?

Original comment by rwstoneb...@gmail.com on 25 Mar 2011 at 5:59

[GoogleCodeExporter]

I've verified that inspector breakpoints work in release build at revision 209.

Original comment by magreenb...@gmail.com on 25 Mar 2011 at 6:49

• Changed state: Fixed

[GoogleCodeExporter]

A binary release at revision 211 is now available.

Original comment by magreenb...@gmail.com on 25 Mar 2011 at 7:27

[GoogleCodeExporter]

You rock, thank you so much for all the help.

Original comment by rwstoneb...@gmail.com on 25 Mar 2011 at 7:32