https://llvm.org/bugs/show_bug.cgi?id=24668
Bug ID: 24668
Summary: Breakpoints not being resolved correctly
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: ztur...@google.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified
A number of tests which are seemingly unrelated fail because they all rely on
being able to set a breakpoint and then have it resolve dynamically once the
executable is run.
In certain instances, this doesn't work correctly on Windows, leading to output
similar to the following:
runCmd: breakpoint list -f
output: Current breakpoints:
1: file = 'main.cpp', line = 36, exact_match = 0, locations = 1
1.1: where = a.out`void * step_thread_func(void) + 3 at main.cpp:36, address
= a.out[0x00412023], unresolved, hit count = 0
Expecting sub string: 1: file = 'main.cpp', line = 36, locations = 1
Not matched
FAIL
Traceback (most recent call last):
File "D:\src\llvm\tools\lldb\test\lldbtest.py", line 615, in wrapper
func(*args, **kwargs)
File "D:\src\llvm\tools\lldb\test\lldbtest.py", line 615, in wrapper
func(*args, **kwargs)
File "D:\src\llvm\tools\lldb\test\lldbtest.py", line 615, in wrapper
func(*args, **kwargs)
File "D:\src\llvm\tools\lldb\test\lldbtest.py", line 551, in wrapper
return func(self, *args, **kwargs)
File
"D:\src\llvm\tools\lldb\test\functionalities\thread\create_during_step\TestCreateDuringStep.py",
line 46, in test_step_inst_with_dwarf
self.create_during_step_inst_test()
File
"D:\src\llvm\tools\lldb\test\functionalities\thread\create_during_step\TestCreateDuringStep.py",
line 75, in create_during_step_inst_test
self.create_during_step_base("thread step-inst -m all-threads", 'stop
reason = instruction step')
File
"D:\src\llvm\tools\lldb\test\functionalities\thread\create_during_step\TestCreateDuringStep.py",
line 95, in create_during_step_base
substrs = ["1: file = 'main.cpp', line = %d, locations = 1" %
self.breakpoint])
File "D:\src\llvm\tools\lldb\test\lldbtest.py", line 2630, in expect
msg if msg else EXP_MSG(str, exe))
AssertionError: False is not True : Breakpoint location shown correctly
As can be seen, the breakpoint is set, but it is unresolved so it has no
breakpoitn locations, causing the test to fail.
This affects (at a minimum) the following set of tests:
TestThreadStates.ThreadStateTestCase.test_process_interrupt_with_dwarf
TestThreadStates.ThreadStateTestCase.test_process_state_with_dwarf
TestCreateDuringStep.CreateDuringStepTestCase.test_step_in_with_dwarf
TestCreateDuringStep.CreateDuringStepTestCase.test_step_inst_with_dwarf
TestCreateDuringStep.CreateDuringStepTestCase.test_step_over_with_dwarf
TestExitDuringBreak.ExitDuringBreakpointTestCase.test_with_dwarf
TestMultipleBreakpoints.MultipleBreakpointTestCase.test_with_dwarf
TestThreadStates.ThreadStateTestCase.test_state_after_breakpoint_with_dwarf
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
