Page MenuHomePhabricator

Please use GitHub pull requests for new patches. Phabricator shutdown timeline

ted (Ted Woodward)
User

Projects

User does not belong to any projects.

User Details

User Since
Mar 13 2014, 1:21 PM (497 w, 6 d)

Recent Activity

Mon, Sep 25

ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Fix comment about "a" registers

Mon, Sep 25, 1:27 PM · Restricted Project, Restricted Project
ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Change "word_size = m_is_rv64 ? 8 : 4" to "word_size = reg_size"

Mon, Sep 25, 1:24 PM · Restricted Project, Restricted Project
ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Remove disabling JIT and enabling IR Interpreter function calls, as requested
by Jason Molenda.

Mon, Sep 25, 1:21 PM · Restricted Project, Restricted Project

Thu, Sep 21

ted added inline comments to D159101: [RISC-V] Add RISC-V ABI plugin.
Thu, Sep 21, 9:17 AM · Restricted Project, Restricted Project

Tue, Sep 19

ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Fix crash when there was no process (found by API tests)
Remove bugs in function call setup when using IR interpreter (found by API tests)
Change flag tests to use lldb_private::Flags (requested by @jasonmolenda )

Tue, Sep 19, 8:31 AM · Restricted Project, Restricted Project

Tue, Sep 12

ted added a comment to D159101: [RISC-V] Add RISC-V ABI plugin.

@DavidSpickett update on testing: I'm running tests. I found an issue in the IR Interpreter when calling class methods. Somehow a 32 bit pointer gets the upper 32 bits in the 64 bit uint it's stored in set to 0xffffffff, which causes an assert. Downstream we've changed the assert should probably to an error so it doesn't take down the debugger. I can make this change here, but I wonder if it should be a separate change. For now I'm skipping the tests that cause this. Progress is slow, but steady.

Tue, Sep 12, 6:22 AM · Restricted Project, Restricted Project

Thu, Aug 31

ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Implement Jason Molenda's request to use an ivar instead of static variables.

Thu, Aug 31, 1:25 PM · Restricted Project, Restricted Project
ted added a comment to D159101: [RISC-V] Add RISC-V ABI plugin.

Great. Could you include that in the commit message? Seems like we get a lot of questions about how mature risc-v support is, so we can point to this as a milestone for that.

Thu, Aug 31, 12:19 PM · Restricted Project, Restricted Project

Wed, Aug 30

ted added a comment to D159101: [RISC-V] Add RISC-V ABI plugin.

I have some vague idea that maybe we could put a hack in the test suite to use the qemu-user platform instead of lldb-server. To at least give it a go, but I haven't tried it myself yet.

Wed, Aug 30, 2:58 PM · Restricted Project, Restricted Project

Tue, Aug 29

ted updated the diff for D159101: [RISC-V] Add RISC-V ABI plugin.

Updated with David Spickett's comments

Tue, Aug 29, 3:05 PM · Restricted Project, Restricted Project
ted added a reviewer for D159101: [RISC-V] Add RISC-V ABI plugin: apazos.
Tue, Aug 29, 3:02 PM · Restricted Project, Restricted Project
ted added inline comments to D159101: [RISC-V] Add RISC-V ABI plugin.
Tue, Aug 29, 2:50 PM · Restricted Project, Restricted Project
ted added a comment to D159101: [RISC-V] Add RISC-V ABI plugin.

Also could you provide a list of things you have tested with qemu. So I can get an idea of how sure we can be any of this works / be a test plan, albeit manual for anyone updating this code in future.

Tue, Aug 29, 12:57 PM · Restricted Project, Restricted Project
ted added reviewers for D159101: [RISC-V] Add RISC-V ABI plugin: jasonmolenda, labath, asb, lewis-revill, compnerd, simoncook, jrtc27, JDevlieghere, aprantl, sven, kasper81, tzb99.

Adding commenters from https://reviews.llvm.org/D62732 as reviewers.

Tue, Aug 29, 11:37 AM · Restricted Project, Restricted Project
ted updated subscribers of D159101: [RISC-V] Add RISC-V ABI plugin.

With this change, I'm able to debug RISC-V 32 and 64 bit applications using Linux user space QEMU, using @labath 's QemuUser platform. Simple expression parsing with the IR Interpreter is working. Complex expression parsing with JIT is not tested.

Tue, Aug 29, 11:30 AM · Restricted Project, Restricted Project
ted requested review of D159101: [RISC-V] Add RISC-V ABI plugin.
Tue, Aug 29, 7:57 AM · Restricted Project, Restricted Project

Aug 22 2023

ted committed rGbe88462cd6aa: Platform qemu-user: Build path to qemu automatically if not specified (authored by ted).
Platform qemu-user: Build path to qemu automatically if not specified
Aug 22 2023, 12:21 PM · Restricted Project
ted closed D155117: Platform qemu-user: Build path to qemu automatically if not specified.
Aug 22 2023, 12:20 PM · Restricted Project, Restricted Project
ted committed rG523110d654a2: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress (authored by ted).
Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress
Aug 22 2023, 12:16 PM · Restricted Project
ted closed D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress.
Aug 22 2023, 12:16 PM · Restricted Project, Restricted Project

Aug 1 2023

ted added a comment to D155117: Platform qemu-user: Build path to qemu automatically if not specified.

I am wondering if we actually need the second step (the architecture setting) here. The main reason it exists is the usage in GetSupportedArchitectures (which is called before a target is created) it seems like the value derived from the target should always be more correct. WDYT? What are the values you get in steps 2 and 3 for your use case?

I don't think we need to specify the architecture, because I think we can always get it from the triple. There might be a case where someone is using a qemu that isn't named the same as the Triple ArchName, but that case could be covered by emulator-path.

Yeah, that's my thinking as well. Given this, I think we should drop the setting part and just go with the target value directly.

Aug 1 2023, 7:56 AM · Restricted Project, Restricted Project
ted added a comment to D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress.

So Ted, can you verify that nothing is missing in RISCV since this is already the way it works for x86/x86_64 and arm32/arm64? I am thinking like Jason is where I wonder if something isn't just hooked up right for RISCV somehow. Or if you can verify that nothing changes for x86/x86_64 or arm32/arm64 if this setting is enabled and there are no symbolication regressions in the comments if this does get enabled for the architectures where it is working as expected...

Aug 1 2023, 7:55 AM · Restricted Project, Restricted Project

Jul 18 2023

ted added a comment to D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress.

Looks like other disassemblers already show full addresses for the branches and calls (at least arm64 does from my output above), so not sure why RISCV would require this setting, but x86_64 and arm64 wouldn't because it is already working that way??

Jul 18 2023, 3:31 PM · Restricted Project, Restricted Project
ted added a comment to D155117: Platform qemu-user: Build path to qemu automatically if not specified.

As for the GetSupportedArchitectures case, downstream I left in the code that checks the property, but changed the return {}; to

return {ArchSpec(llvm::Triple("riscv32-unknown-linux")),
        ArchSpec(llvm::Triple("riscv64-unknown-linux"))};
Jul 18 2023, 12:23 PM · Restricted Project, Restricted Project
ted added a comment to D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress.

Isn't it better to print branches within a function as an offset, given that our disassembly format by default lists the offset of each instruction. So instead of looking for a 6-digit long hex address, you're looking for a decimal offset in the output? I'm not sure if you disagree with my opinion, or if you have an example where it is clearer to have an address that I'm not seeing.

Jul 18 2023, 7:23 AM · Restricted Project, Restricted Project
ted added a comment to D155117: Platform qemu-user: Build path to qemu automatically if not specified.

I am wondering if we actually need the second step (the architecture setting) here. The main reason it exists is the usage in GetSupportedArchitectures (which is called before a target is created) it seems like the value derived from the target should always be more correct. WDYT? What are the values you get in steps 2 and 3 for your use case?

Jul 18 2023, 7:13 AM · Restricted Project, Restricted Project

Jul 13 2023

ted added a reviewer for D155117: Platform qemu-user: Build path to qemu automatically if not specified: labath.
Jul 13 2023, 8:15 AM · Restricted Project, Restricted Project

Jul 12 2023

ted requested review of D155117: Platform qemu-user: Build path to qemu automatically if not specified.
Jul 12 2023, 2:09 PM · Restricted Project, Restricted Project
ted added reviewers for D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress: teemperor, JDevlieghere.
Jul 12 2023, 12:31 PM · Restricted Project, Restricted Project
ted requested review of D155107: Add support for llvm::MCInstPrinter::setPrintBranchImmAsAddress.
Jul 12 2023, 12:30 PM · Restricted Project, Restricted Project
ted committed rGded1bad64af0: Fix mixed disassembly showing source lines for "line 0" (authored by ted).
Fix mixed disassembly showing source lines for "line 0"
Jul 12 2023, 9:40 AM · Restricted Project
ted closed D112931: Fix mixed disassembly showing source lines for "line 0".
Jul 12 2023, 9:39 AM · Restricted Project, Restricted Project

Nov 8 2021

ted added a comment to D112931: Fix mixed disassembly showing source lines for "line 0".

@jasonmolenda friendly ping

Nov 8 2021, 12:35 PM · Restricted Project, Restricted Project

Nov 3 2021

ted added a comment to D111209: Don't push null ExecutionContext on CommandInterpreter exectx stack.

@jasonmolenda I discovered the same issue in another way - create a python command and load it with "command script import". Here is test.py:

Nov 3 2021, 7:16 AM · Restricted Project, Restricted Project

Nov 2 2021

ted added inline comments to D112931: Fix mixed disassembly showing source lines for "line 0".
Nov 2 2021, 9:22 AM · Restricted Project, Restricted Project
ted added inline comments to D112931: Fix mixed disassembly showing source lines for "line 0".
Nov 2 2021, 7:58 AM · Restricted Project, Restricted Project

Nov 1 2021

ted added inline comments to D112931: Fix mixed disassembly showing source lines for "line 0".
Nov 1 2021, 3:47 PM · Restricted Project, Restricted Project
ted committed rG1c05c52de217: [lldb-vscode] Fix coredump load source mapping for first file (authored by ted).
[lldb-vscode] Fix coredump load source mapping for first file
Nov 1 2021, 8:48 AM
ted closed D112834: [lldb-vscode] Fix coredump load source mapping for first file.
Nov 1 2021, 8:48 AM · Restricted Project
ted added reviewers for D112931: Fix mixed disassembly showing source lines for "line 0": clayborg, jingham, labath, jasonmolenda.
Nov 1 2021, 8:36 AM · Restricted Project, Restricted Project
ted updated the diff for D112931: Fix mixed disassembly showing source lines for "line 0".

Fix test to exit lldb

Nov 1 2021, 8:34 AM · Restricted Project, Restricted Project
ted requested review of D112931: Fix mixed disassembly showing source lines for "line 0".
Nov 1 2021, 8:28 AM · Restricted Project, Restricted Project

Oct 29 2021

ted added a reviewer for D112834: [lldb-vscode] Fix coredump load source mapping for first file: labath.
Oct 29 2021, 10:26 AM · Restricted Project
ted added a reviewer for D112834: [lldb-vscode] Fix coredump load source mapping for first file: wallace.
Oct 29 2021, 10:16 AM · Restricted Project
ted added a reviewer for D112834: [lldb-vscode] Fix coredump load source mapping for first file: clayborg.
Oct 29 2021, 10:15 AM · Restricted Project
ted requested review of D112834: [lldb-vscode] Fix coredump load source mapping for first file.
Oct 29 2021, 10:09 AM · Restricted Project

Oct 8 2021

ted added a comment to D109738: [lldb] Fix bug 38317 - Address breakpoints don't work if set before the process launches.

That is clearly wrong: an address is never enough to restore a breakpoint from one session to the next even if you can turn ASLR off. After all, the breakpoint could be in a dlopened library.

Oct 8 2021, 3:04 PM · Restricted Project

Oct 5 2021

ted added inline comments to D111136: [lldb] [DynamicRegisterInfo] Support iterating over registers().
Oct 5 2021, 7:42 AM · Restricted Project
ted added inline comments to D111131: [LLDB] Round XML register bitsize to byte boundary.
Oct 5 2021, 7:38 AM · Restricted Project

Sep 23 2021

ted committed rG953ddded1aa2: [lldb] Handle malformed qfThreadInfo reply (authored by ted).
[lldb] Handle malformed qfThreadInfo reply
Sep 23 2021, 3:04 PM
ted closed D109937: [lldb] Handle malformed qfThreadInfo reply.
Sep 23 2021, 3:04 PM · Restricted Project

Sep 22 2021

ted added a comment to D109937: [lldb] Handle malformed qfThreadInfo reply.

Prints were there for my debugging. They don't serve a purpose, so I've removed them.

Sep 22 2021, 7:45 AM · Restricted Project
ted updated the diff for D109937: [lldb] Handle malformed qfThreadInfo reply.

Remove unneeded prints from test

Sep 22 2021, 7:43 AM · Restricted Project

Sep 21 2021

ted updated the diff for D109937: [lldb] Handle malformed qfThreadInfo reply.

[lldb] Handle malformed qfThreadInfo reply

Sep 21 2021, 3:20 PM · Restricted Project

Sep 17 2021

ted added a comment to D109937: [lldb] Handle malformed qfThreadInfo reply.

I've got a test written. It doesn't crash like the debugger in the wild does, but it does give a tid of 0 for each thread I ask about. So I can assert if the threads don't have the correct tid.

Sep 17 2021, 12:35 PM · Restricted Project
ted added a comment to D109937: [lldb] Handle malformed qfThreadInfo reply.

I agree about the test. I'll work on one.

Sep 17 2021, 8:01 AM · Restricted Project

Sep 16 2021

ted added reviewers for D109937: [lldb] Handle malformed qfThreadInfo reply: jingham, labath.
Sep 16 2021, 4:42 PM · Restricted Project
ted requested review of D109937: [lldb] Handle malformed qfThreadInfo reply.
Sep 16 2021, 4:41 PM · Restricted Project

Sep 15 2021

ted committed rG17589538aaef: [lldb-vscode] Fix focus thread when previous thread exits (authored by ted).
[lldb-vscode] Fix focus thread when previous thread exits
Sep 15 2021, 4:10 PM
ted closed D109633: [lldb-vscode] Fix focus thread when previous thread exits.
Sep 15 2021, 4:09 PM · Restricted Project
ted added a comment to D109738: [lldb] Fix bug 38317 - Address breakpoints don't work if set before the process launches.

BTW, do you know what change made this stop working?

Sep 15 2021, 3:55 PM · Restricted Project

Sep 14 2021

ted added a comment to D109738: [lldb] Fix bug 38317 - Address breakpoints don't work if set before the process launches.

I created the original bug because a change made LLDB stop working on address breakpoints if they were created before the program is run. Setting a breakpoint on an address is a typical case with embedded applications, especially if you want to debug startup code.

Sep 14 2021, 2:30 PM · Restricted Project

Sep 10 2021

ted requested review of D109633: [lldb-vscode] Fix focus thread when previous thread exits.
Sep 10 2021, 2:48 PM · Restricted Project

Jul 26 2021

ted accepted D106832: [lldb] [gdb-remote client] Avoid zero padding PID/TID in H packet.

LGTM. Thanks Michał!

Jul 26 2021, 3:22 PM · Restricted Project

May 28 2021

ted added a comment to D99901: [Driver][test] Test intended target only.

Why would we not want to support this on other targets, like Arm? Fixes for AIX shouldn't impact other things.

May 28 2021, 7:31 AM · Restricted Project

Aug 5 2020

ted committed rG3169d920ccd1: Remove special Hexagon packet traversal code (authored by ted).
Remove special Hexagon packet traversal code
Aug 5 2020, 10:06 AM
ted closed D84966: Remove special Hexagon packet traversal code.
Aug 5 2020, 10:05 AM · Restricted Project

Aug 3 2020

ted updated the diff for D84966: Remove special Hexagon packet traversal code.

Fixed formatting flagged by Lint: Pre-merge checks

Aug 3 2020, 8:53 AM · Restricted Project

Jul 30 2020

ted requested review of D84966: Remove special Hexagon packet traversal code.
Jul 30 2020, 11:39 AM · Restricted Project

Apr 29 2020

ted added a comment to D78801: [LLDB] Add class WasmProcess for WebAssembly debugging.

Hi Paulo,
@clayborg asked me to look at this, because I've worked with systems that have multiple address spaces. I was thinking, instead of a WebAssembly specific memory read, we should implement an optional generic memory read and write with memory space support.

Apr 29 2020, 10:43 AM · Restricted Project, Restricted Project

Feb 13 2020

ted committed rGefef165f82cb: Clean up hexagon builder after object-emission removal (authored by ted).
Clean up hexagon builder after object-emission removal
Feb 13 2020, 11:20 AM
ted committed rGcecc185166c0: Add REQUIRES: x86 so this won't be run if x86 is not available. (authored by ted).
Add REQUIRES: x86 so this won't be run if x86 is not available.
Feb 13 2020, 9:20 AM

Feb 10 2020

ted committed rG7683a084de6b: Remove lit feature object-emission (authored by ted).
Remove lit feature object-emission
Feb 10 2020, 1:58 PM
ted closed D73568: Remove lit feature object-emission.
Feb 10 2020, 1:58 PM · Restricted Project
ted updated the diff for D73568: Remove lit feature object-emission.

File llvm/test/DebugInfo/X86/vla.ll was modified so the diff did not apply anymore. object-emission was removed from it, so I'm removing it from this diff.

Feb 10 2020, 12:45 PM · Restricted Project
ted committed rG6fd818c5a9c5: Don't fail step out if remote server doesn't implement qMemoryRegionInfo (authored by ted).
Don't fail step out if remote server doesn't implement qMemoryRegionInfo
Feb 10 2020, 11:42 AM
ted closed D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.
Feb 10 2020, 11:41 AM · Restricted Project

Feb 5 2020

ted added a comment to D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.

@jingham friendly ping

Feb 5 2020, 1:12 PM · Restricted Project
ted added a comment to D73568: Remove lit feature object-emission.

Friendly ping

Feb 5 2020, 1:12 PM · Restricted Project

Jan 28 2020

ted reopened D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.
Jan 28 2020, 1:55 PM · Restricted Project
ted updated the diff for D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.

Removed the code that sets m_constructor_errors when GetLoadAddressPermissions returns False, as requested by @jingham .

Jan 28 2020, 1:55 PM · Restricted Project
ted added a comment to D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.

Wow @jingham you posted your comment and I landed the patch at the same time!

Jan 28 2020, 1:11 PM · Restricted Project
ted committed rG04488c485a88: Don't fail step out if remote server doesn't implement qMemoryRegionInfo (authored by ted).
Don't fail step out if remote server doesn't implement qMemoryRegionInfo
Jan 28 2020, 11:47 AM
ted closed D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.
Jan 28 2020, 11:46 AM · Restricted Project
Herald added a reviewer for D73568: Remove lit feature object-emission: whitequark.
Jan 28 2020, 11:22 AM · Restricted Project

Jan 10 2020

ted added a reviewer for D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo: mossberg.
Jan 10 2020, 9:23 AM · Restricted Project
ted added a comment to D71372: [lldb] Add additional validation on return address in 'thread step-out'.
In D71372#1813142, @ted wrote:
In D71372#1810687, @ted wrote:

I've got another failure case for this. If the remote gdbserver doesn't implement qMemoryRegionInfo or qXfer:memory-map:read, thread step-out will fail.
....

That's a good point Ted. I think we should give targets which don't support fetching permissions the benefit of the doubt, and treat all memory as potentially executable. Would removing the return statement from the if(!GetLoadAddressPermissions) branch solve your problem? If so, can you whip up a patch for that?

Removing the return statement fixes the issue. I'll put up a patch. Keeping the m_constructor_errors.Printf line doesn't cause a failure; it might be useful to keep that in case the breakpoint can't be created for other reasons. What do you think?

I don't care much either way.. Since you have this kind of a target around, you can judge whether printing this error/warning after each "finish" would be useful or just annoying. Another possibility would be to don't print the error to the command output, but still emit something into the log...

Jan 10 2020, 8:25 AM · Restricted Project
ted added reviewers for D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo: labath, jingham, clayborg.
Jan 10 2020, 8:25 AM · Restricted Project
ted created D72513: Don't fail step out if remote server doesn't implement qMemoryRegionInfo.
Jan 10 2020, 8:24 AM · Restricted Project

Jan 9 2020

ted added a comment to D71372: [lldb] Add additional validation on return address in 'thread step-out'.
In D71372#1810687, @ted wrote:

I've got another failure case for this. If the remote gdbserver doesn't implement qMemoryRegionInfo or qXfer:memory-map:read, thread step-out will fail.
....

That's a good point Ted. I think we should give targets which don't support fetching permissions the benefit of the doubt, and treat all memory as potentially executable. Would removing the return statement from the if(!GetLoadAddressPermissions) branch solve your problem? If so, can you whip up a patch for that?

Jan 9 2020, 2:37 PM · Restricted Project

Jan 8 2020

ted added a comment to D71372: [lldb] Add additional validation on return address in 'thread step-out'.

I've got another failure case for this. If the remote gdbserver doesn't implement qMemoryRegionInfo or qXfer:memory-map:read, thread step-out will fail.

Jan 8 2020, 12:32 PM · Restricted Project
ted added a comment to D69119: Modernize the rest of the Find.* API (NFC).
Jan 8 2020, 12:32 PM · Restricted Project

Apr 4 2019

ted added a comment to D60152: Fix and simplify PrepareCommandsForSourcing.

llvm/tools/lldb/tools/driver/Driver.cpp:495:12: error: comparison of integers of different signs: 'ssize_t' (aka 'long') and 'size_t' (aka 'unsigned long') [-Werror,-Wsign-compare]

if (nrwr != commands_size) {
    ~~~~ ^  ~~~~~~~~~~~~~

1 error generated.

Apr 4 2019, 11:38 AM · Restricted Project

Mar 25 2019

ted added a comment to D59719: [ScriptInterpreter] Make sure that PYTHONHOME is right..

This doesn't look correct to me - it looks like there are 1 too many #endifs. I think the one at line 179 should be removed - it should have been replaced by the #else that is at line 180.

Mar 25 2019, 1:17 PM · Restricted Project, Restricted Project

Feb 1 2019

ted added a comment to D57552: Handle "." in target.source-map in PathMapListing::FindFiles.

That sounds like it will have to be fixed somewhere else, and not part of this patch then. Can you file a bug to get that fixed?

Feb 1 2019, 11:36 AM · Restricted Project, Restricted Project
ted added a comment to D57552: Handle "." in target.source-map in PathMapListing::FindFiles.
In D57552#1380782, @ted wrote:

FYI, @jingham , this is also an issue with DYLD plugins, if the file in the link map starts with ".". "image search-paths add . /path/to/my/libraries" fails in this case, because "./library.so" gets changed to "library.so".

This should fix that issue as well, since image search-paths are also PathMappingLists. I don't see any tests for this, however. Do you have something handy you could turn into a test?

Feb 1 2019, 10:39 AM · Restricted Project, Restricted Project
Herald added a project to D55332: [CMake] Python bindings generation polishing: Restricted Project.

@sgraenitz I've found an issue with this patch, using the Visual Studio 2015 generator.

Feb 1 2019, 8:16 AM · Restricted Project
ted added a comment to D57552: Handle "." in target.source-map in PathMapListing::FindFiles.

FYI, @jingham , this is also an issue with DYLD plugins, if the file in the link map starts with ".". "image search-paths add . /path/to/my/libraries" fails in this case, because "./library.so" gets changed to "library.so".

Feb 1 2019, 7:40 AM · Restricted Project, Restricted Project

Sep 10 2018

ted added a comment to D51162: [PDB] Restore AST from PDB symbols.

Another issue:

Sep 10 2018, 2:55 PM · Restricted Project
ted committed rLLDB341849: Fix raw address breakpoints not resolving.
Fix raw address breakpoints not resolving
Sep 10 2018, 11:20 AM