Add text location in debugger event

Add text location in debugger event

- Adding token number in text location data. Line number will be
  removed when the editor knows how to convert a token number to its
  line number.
- "location" field in stack frames is now optional. If it is not present, there
  is no corresponding textual location for the code location.
- Add location info of "paused" and "interrupted" events.
  Stack trace will go away in these events.
Committed: https://code.google.com/p/dart/source/detail?r=20816

[Tom Ball, 2013-04-02 16:24:54]

lgtm

https://codereview.chromium.org/13144018/diff/2002/runtime/bin/dbg_message.cc
File runtime/bin/dbg_message.cc (right):

https://codereview.chromium.org/13144018/diff/2002/runtime/bin/dbg_message.cc...
runtime/bin/dbg_message.cc:948: // trace from the paused event in the wire
protocol.
We should be able to remove it now, if the editor checks for a null after
fetching that parameter, like it should for all JSON object fields.

[hausner, 2013-04-02 17:15:23]

https://codereview.chromium.org/13144018/diff/2002/runtime/bin/dbg_message.cc
File runtime/bin/dbg_message.cc (right):

https://codereview.chromium.org/13144018/diff/2002/runtime/bin/dbg_message.cc...
runtime/bin/dbg_message.cc:948: // trace from the paused event in the wire
protocol.
On 2013/04/02 16:24:54, Tom Ball wrote:
> We should be able to remove it now, if the editor checks for a null after
> fetching that parameter, like it should for all JSON object fields.
True. But i want to make sure the editor/debugger shows a valid stack trace. For
that, it would have to issue a getStackTrace command in addition to the null
check you mention.

I think this will go away very soon, hopefully with the next change when the
editor is updated.

[devoncarew, 2013-04-02 20:20:53]

lgtm

This looks fine from the editor side. I'll prepare a CL which removes use of the
deprecated JSON fields.

[hausner, 2013-04-02 20:41:34]

Committed patchset #4 manually as r20816 (presubmit successful).