My spidey sense would guess that you set the breakpoint in the Browser
process, when V8 and WebKit run in the Renderer process.
Good luck
-- dean
2009/5/29 Lucius Fox lucius.fo...@gmail.com:
Thank you.
I tried your suggestion on XCode on MacOS. But it still does not break for me.
I set a
I just re-read your post and realized you were using test_shell, which
is single process. In that case, I am not sure what the problem is,
and have no experience with xcode.
Sorry, good luck
On Fri, May 29, 2009 at 11:06 AM, Dean McNameede...@chromium.org wrote:
My spidey sense would guess
Xcode can have problems properly setting breakpoints in subprojects. There
are two ways to work around this:
- Uncheck the Load *symbols lazily option in Xcode's debugging
preferences.*
- Open up the gdb console window and set breakpoints from the gdb command
line
--Amanda
2009/5/29 Lucius Fox
Hi,
There must be something wrong with your setting of break points. There is
only on way of getting JavaScript code into V8 from a client application,
and that is through the static method v8::Script::Compile in the public API.
This method is defined in api.cc where it in turn calls
Thanks. This is helpful.
2009/5/27 Søren Gjesse sgje...@chromium.org:
Hi,
There must be something wrong with your setting of break points. There is
only on way of getting JavaScript code into V8 from a client application,
and that is through the static method v8::Script::Compile in the
Thank you.
I tried your suggestion on XCode on MacOS. But it still does not break for me.
I set a break point at:
LocalScript Script::Compile(v8::HandleString source,
v8::ScriptOrigin* origin,
v8::ScriptData* script_data) {
