Breakpoint tests fail on Windows

[llvmbot]

Bugzilla Link	24528
Version	unspecified
OS	Windows NT
Blocks	#22140
Reporter	LLVM Bugzilla Contributor
CC	@stella.stamenova

Extended Description

From the log it looks like something having to do with pending breakpoint resolution is not working correctly, so maybe the problem is in DynamicLoaderWindows somewhere.

runCmd: breakpoint list -f
output: Current breakpoints:
1: file = 'D:\src\llvm\tools\lldb\test\functionalities\breakpoint\breakpoint_command\main.c', line = 12, exact_match = 0, locations = 0 (pending)

3: file = 'main.c', line = 12, exact_match = 0, locations = 0 (pending)
Breakpoint commands:
return bktptcmd.function(frame, bp_loc, internal_dict)

5: regex = '._MyFunction', locations = 0 (pending)

6: regex = '._MyFunction', locations = 0 (pending)

7: regex = '._MyFunction', locations = 0 (pending)

8: source regex = "is about to return [12]0", exact_match = 0, locations = 0 (pending)

9: source regex = "is about to return [12]0", exact_match = 0, locations = 0 (pending)

Expecting pattern: 1: file = '.*main.c', line = 12, exact_match = 0, locations = 1, resolved = 1
Not matched

FAIL

<bound method SBProcess.Kill of <lldb.SBProcess; proxy of <Swig Object of type 'lldb::SBProcess *' at 0x032DD6B8> >>: success

Executing tearDown hook: self.addTearDownHook(lambda: self.runCmd("settings clear auto-confirm"))

[llvmbot]

This also causes TestBreakpointLocations.py to fail on Windows for a similar reason. I suspect they are the same underlying cause.

[stella.stamenova]

The scripted breakpoint tests in TestScriptedResolver also fail because of this (most likely).

[stella.stamenova]

TestScriptedResolver.py
TestBreakpointLocations.py

are all the tests that are currently marked as failing because of this bug.