hausner@google.com f5dd5598ac Don’t set more than one code breakpoint per token position ...

Some time ago when operator== calls had inlined null checks at
the call site, the debugger had to instrument multiple code breakpoints
that were all mapping to the same source position. This is no longer
necessary. This change makes sure we set a code breakpoint only at
the lowest compiled code address, so that expressions like i++ no longer
result in 2 or 3 breakpoints (one each for load filed, add, store field).

Fixes 18397.

R=srdjan@google.com

Review URL: https://codereview.chromium.org//256243002

git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@35510 260f80e4-7a28-3924-810f-c04153c831b5

2014-04-28 23:40:34 +00:00

..

bin

Adds AI_ADDRCONFIG back to address lookup on Android.

2014-04-25 14:45:34 +00:00

include

Support evaluation of expressions in context of a stack frame

2014-04-23 22:56:23 +00:00

lib

Prevent unbounded growth of the getField/setField closure caches.

2014-04-25 17:47:15 +00:00

platform

Make opendir test for EINTR again and make NO_RETRY_EXPECTED check in release mode.

2014-04-24 06:38:16 +00:00

tests/vm

Generate escape sequence for non-printable ascii characters

2014-04-24 22:55:52 +00:00

third_party

- Assertions need to "touch" their conditions to avoid errors such as:

2014-02-28 18:24:24 +00:00

tools

Replace '\' with '' in resources table

2014-02-12 17:26:27 +00:00

vm

Don’t set more than one code breakpoint per token position

2014-04-28 23:40:34 +00:00

.gitignore

…

codereview.settings

…

dart-runtime.gyp

- Make sure sample_extension is built.

2013-11-06 21:46:30 +00:00

PRESUBMIT.py

- Add more data collection to the scavenger.

2013-10-16 23:15:11 +00:00