This is an archive of the discontinued LLVM Phabricator instance.

New test for llvm.org/pr23478
ClosedPublic

Authored by tberghammer on May 11 2015, 7:18 AM.

Details

Summary

New test for llvm.org/pr23478

When there is two brekapoint on two consecutive instruction then
the second breakpoint is ignored by lldb. This test check for the
correct behavior in this scenario.

Diff Detail

Repository
rL LLVM

Event Timeline

tberghammer retitled this revision from to New test for llvm.org/pr23478.
tberghammer updated this object.
tberghammer edited the test plan for this revision. (Show Details)
tberghammer added a reviewer: labath.
tberghammer added a subscriber: Unknown Object (MLST).
labath accepted this revision.May 11 2015, 7:36 AM
labath edited edge metadata.

Very nice catch. OK to commit after fixing two small issues.

test/functionalities/breakpoint/consecutive_breakpoins/TestConsecutiveBreakpoints.py
33 ↗(On Diff #25467)

I think it's better to avoid hard-coding line numbers. Most of the test suite uses markers like "// Set breakpoint here" in the source code to place breakpoints.

66 ↗(On Diff #25467)

Do you want this to stay here? If so, maybe put "The address of the second breakpoint is: " before the actual address.

This revision is now accepted and ready to land.May 11 2015, 7:36 AM
tberghammer added inline comments.May 11 2015, 7:45 AM
test/functionalities/breakpoint/consecutive_breakpoins/TestConsecutiveBreakpoints.py
33 ↗(On Diff #25467)

Done

66 ↗(On Diff #25467)

Nice catch, it was just for debugging

This revision was automatically updated to reflect the committed changes.