LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 21765 - Cannot call a function in the debugee on Windows.
Summary: Cannot call a function in the debugee on Windows.
Status: NEW
Alias: None
Product: lldb
Classification: Unclassified
Component: All Bugs (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P normal
Assignee: Adrian McCarthy
URL:
Keywords:
Depends on:
Blocks: 21766
  Show dependency tree
 
Reported: 2014-12-05 13:25 PST by Zachary Turner
Modified: 2018-12-19 11:09 PST (History)
3 users (show)

See Also:
Fixed By Commit(s):


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zachary Turner 2014-12-05 13:25:04 PST
This can be reproduced via the following command line:

d:\src\llvm\build\ninja>D:\python_src\Python-2.7.8\PCbuild\python_d.exe  D:\src\llvm\tools\lldb\test/dotest.py -t -q --arch=i686 --executable D:/src/llvm/build/ninja/bin/lldb.exe -s D:/src/llvm/build/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS -C D:\src\llvm\build\ninja\bin\clang.exe -p TestCallWithTimeout.py D:\src\llvm\tools\lldb\test\expression_command\timeout


At some point during the run of the test, the test tries to call a function that exists in the debugee.  Parsing this expression fails and it says it cannot find the symbol in the target.
Comment 1 Zachary Turner 2014-12-05 14:40:21 PST
Assigning to majnemer as it might be a mangling issue, which he has some expertise in.

You can put the breakpoint in all overloads of SBFrame::EvaluateExpression in SBFrame.cpp to step through the failing method.
Comment 2 Zachary Turner 2015-08-20 15:31:45 PDT
This is also affecting the following test suites.

TestCPPStaticMethods.py
TestCStrings.py
TestExprHelpExamples.py
TestExprs.py
TestFormatters.py
TestFunctionTypes.py
TestNestedPersistentTypes.py
TestPersistentTypes.py
TestPrintfAfterUp.py
TestSetValues.py
Comment 3 Adrian McCarthy 2018-02-26 13:26:55 PST
The test that references this bug is passing, and the bug this one supposedly blocks is fixed, so I think this is fixed.  I'm about to un-XFAIL the test (TestCallStdSTringFunction.test), at which point I'll close this one.
Comment 4 Adrian McCarthy 2018-02-26 16:43:15 PST
The test is passing for the wrong reasons, so maybe this is still an issue.  Needs more investigation.
Comment 5 Stella Stamenova 2018-05-17 10:03:47 PDT
TestCallOverriddenMethod
TestExprsBug35310

are also failing because of this bug
Comment 6 Zachary Turner 2018-05-17 10:12:23 PDT
Can you try the patch here:

https://bugs.llvm.org/show_bug.cgi?id=37485

And see if it fixes the issue?  This bug just came through today, I expect it will fix some kind of issues with the test suite, but it's hard to know what without trying it.
Comment 7 Stella Stamenova 2018-05-17 11:11:46 PDT
All of these tests are still failing with the patch
Comment 8 Zachary Turner 2018-05-17 11:12:34 PDT
Oh well, was worth a try.  Thanks for checking
Comment 9 Stella Stamenova 2018-12-19 11:09:53 PST
This is the full list of tests that are marked as failing because of this bug right now:

TestCallWithTimeout.py
TestFormatters.py
TestFunctionTypes.py
TestCallOverriddenMethod.py
TestCallStdStringFunction.py
TestTargetAPI.py
TestNameLookup.py
TestSymbolAPI.py
TestDisasmAPI.py
TestCPPStaticMembers.py
TestXValuePrinting.py
TestIRInterpreter.py
TestExpressionInSyscall.py

Several that had been marked are now passing. It is possible that some of them are false positives, but there's a large number of unexpectedly passing tests on Windows now, so I am bulk un-xfailing them, so that we can make the Buildbot green.