- User Since
- Aug 15 2016, 6:00 AM (232 w, 2 d)
Remove unused copy-pasted class method declarations.
Mon, Jan 25
Removed unused REG_CONTEXT_SIZE.
Sat, Jan 23
Fri, Jan 22
Is there a specific reason you've only covered x0..x7 in the test?
Sun, Jan 17
You seem to be removing more than adding there.
Tue, Jan 12
Change the patch to remove the hack entirely.
I can confirm that it builds fine without that block and that there are no changes in CMakeCache.txt.
Trying to add people responsible for the DragonFly part.
Wed, Jan 6
I suppose this has waited long enough to deserve another test run.
Sat, Jan 2
Dec 21 2020
Fixed FPR writing bug, updated tests and removed anonymous namespace.
Dec 20 2020
Dec 18 2020
Dec 17 2020
Made sources conditional to platform via CMake. If this is good, I'll update FreeBSD afterwards.
Dec 16 2020
Dec 15 2020
Dec 14 2020
Compare using weak_ptr to the interpreter module.
Dec 13 2020
Dec 12 2020
Another fix: we should only unload duplicate ld.so if it's actually a duplicate, i.e. the path differs. Otherwise, we've ended up unloading the only copy.
Dec 11 2020
Updated to unload duplicate ld.so as suggested by @labath.
Dec 10 2020
Avoid adding duplicate entry for ld-linux.
One possible hackaround would be to do this only if 1st breakpoint hit is consistent (vs add on Linux), or just make the whole logic #if defined(__FreeBSD__).
Actually, I can still reproduce the double symbol problem with Arch's ld-2.32.so. I can't figure out what's wrong.
Dec 8 2020
This is half-guesswork since platform command seems to be undocumented, so I'd appreciate any suggestions what I got wrong.
Dec 7 2020
Updated to perform the logic inside DynamicLoaderPOSIXDYLD, without touching DYLDRendezvous. This is much safer, and does not cause the double-load of ld-linux.
This causes ld-linux to be added twice on Linux. I need to change the logic a bit.
Rewritten the test wrt comments, that is:
- Added a breakpoint-continue to ensure that the program is past all initial work before we test it.
- Print a global variable to test it.
Dec 6 2020
Added an explanatory comment.
Dec 4 2020
With D92667, I've finally found a way to reproduce this without running lldb-server explicitly — we need to spawn the program via relative path though. I've added a test that does that, and compares the address from image list with the one gotten after explicitly creating target via file path. This clearly reproduces the problem if you don't modify the sources (i.e. mismatch between 0x400000 and 0x200000).
Updated as discussed on IRC, to instead add libs returned by the first 'take snapshot' action.
@thakis, you seem to have been touching lld recently.
Dec 1 2020
Full logs below.
I've added some more debug as requested, and it confirmed that Linux and FreeBSD dyld are behaving differently here.
Nov 30 2020
GDB indeed handles it somehow. I'm going to investigate.
Nov 29 2020
Nov 28 2020
Nov 26 2020
I was referring to:
I disagree. Since we're repeating gdb protocol, it would be nice to use offsets consistent with the gdb protocol, even if it means some extra padding. I do realize that this is broken right now and not trivially fixable but I don't think we should make things worse.
Nov 23 2020
Added system-debugserver feature to skip tests.
Rebase and fix TestRegisters.