Re: [lldb-dev] A problem with the arm64 unwind plans I'm looking at

Hi Jason, I thought about this situation when implemented the original branch following code and haven't been able to come up with a really good solution. My only idea is the same what you mentioned. We should try to recognize all unconditional branches and returns (but not calls) and then if the

[lldb-dev] [Bug 30568] [lldb-mi] -var-assign doesn't accept some valid values

https://llvm.org/bugs/show_bug.cgi?id=30568 abidh changed: What|Removed |Added CC||abidh@gmail.com Assignee|lldb-dev@lists.l

[lldb-dev] [Bug 30265] LLDB-MI: environment-cd doesn't change working directory for inferior

https://llvm.org/bugs/show_bug.cgi?id=30265 abidh changed: What|Removed |Added CC||abidh@gmail.com Assignee|lldb-dev@lists.l

[lldb-dev] unittests/SymbolFile/PDB/Inputs/test-pdb.exe

Over in the Swift GitHub, somebody filed: https://bugs.swift.org/browse/SR-3147 with the claim that this file contains a trojan? Dunno if this is bogus or not, but it's worth somebody on the Windows side checking it out... Jim ___ lldb-dev mailing l

Re: [lldb-dev] unittests/SymbolFile/PDB/Inputs/test-pdb.exe

The source code is here: https://llvm.org/svn/llvm-project/lldb/branches/google/testing/unittests/SymbolFile/PDB/Inputs/test-pdb.cpp And it definitely does nothing. Most of these AV are heuristic, it's probably suspicious about the fact that it's linked with unusual settings (ie /nodefaultlib) wh