tree 50830ce10a63def20a05e5a5660434472366d454
parent f610c0597e001cb1043aa4074afe25ae79a800e3
author Sebastien Hertz <shertz@google.com> 1418830550 +0100
committer Sebastien Hertz <shertz@google.com> 1418835140 +0100

JDWP: fix setting multiple breakpoints in the same method

When setting multiple breakpoints in the same method, we were
incorrectly setting the deoptimization kind of all the breakpoints
set after a first breakpoint. This resulted in incorrect
deoptimization/undeoptimization and even an abort. This was caught
by running the debugger with sanity checks enabled with libartd.so.

We now set next breakpoints with the deoptimization kind of the first
existing breakpoint (if any) so we trigger right [un]deoptimization
when adding or removing a breakpoint.

Bug: 18782753
Bug: 18651686
Change-Id: Idf36ede73302fba83a154052bef701bedc8bc726