Remove DebuggerAgent.

Remove DebuggerAgent.

R=svenpanne@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=21315

[Sven Panne, 2014-05-14 08:38:23]

LGTM, but let's wait a little bit before committing to see if there are any
complaints on v8-users.

[Yang, 2014-05-14 16:28:59]

Committed patchset #2 manually as r21315 (presubmit successful).

[yurys, 2014-05-23 12:30:07]

Now that v8's debug agent is removed what is the current way for debugging
Node.js?

I'm also curious if it's a part of a bigger debugger clean-up and if so are you
going to remove other methods related to v8 built-in debugging protocol?

[Yang, 2014-05-23 12:32:48]

On 2014/05/23 12:30:07, yurys wrote:
> Now that v8's debug agent is removed what is the current way for debugging
> Node.js?
> 
> I'm also curious if it's a part of a bigger debugger clean-up and if so are
you
> going to remove other methods related to v8 built-in debugging protocol?

I wrote a post to v8-users upfront. I expect Node.js to implement the agent by
themselves. I don't think that including the socket connection should be part of
v8.

I'll leave the implementation of the debugging protocol though, since
Debug::SendCommand should still work.

[yurys, 2014-05-23 12:35:04]

On 2014/05/23 12:32:48, Yang wrote:
> On 2014/05/23 12:30:07, yurys wrote:
> > Now that v8's debug agent is removed what is the current way for debugging
> > Node.js?
> > 
> > I'm also curious if it's a part of a bigger debugger clean-up and if so are
> you
> > going to remove other methods related to v8 built-in debugging protocol?
> 
> I wrote a post to v8-users upfront. I expect Node.js to implement the agent by
> themselves. I don't think that including the socket connection should be part
of
> v8.
> 
> I'll leave the implementation of the debugging protocol though, since
> Debug::SendCommand should still work.

Got it. Thanks for clarifying!