User Details
- User Since
- Mar 13 2014, 1:21 PM (433 w, 5 d)
Nov 8 2021
@jasonmolenda friendly ping
Nov 3 2021
@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 2 2021
Nov 1 2021
Fix test to exit lldb
Oct 29 2021
Oct 8 2021
Oct 5 2021
Sep 23 2021
Sep 22 2021
Prints were there for my debugging. They don't serve a purpose, so I've removed them.
Remove unneeded prints from test
Sep 21 2021
[lldb] Handle malformed qfThreadInfo reply
Sep 17 2021
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.
I agree about the test. I'll work on one.
Sep 16 2021
Sep 15 2021
Sep 14 2021
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 10 2021
Jul 26 2021
LGTM. Thanks Michał!
May 28 2021
Why would we not want to support this on other targets, like Arm? Fixes for AIX shouldn't impact other things.
Aug 5 2020
Aug 3 2020
Fixed formatting flagged by Lint: Pre-merge checks
Jul 30 2020
Apr 29 2020
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.
Feb 13 2020
Feb 10 2020
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 5 2020
@jingham friendly ping
Friendly ping
Jan 28 2020
Removed the code that sets m_constructor_errors when GetLoadAddressPermissions returns False, as requested by @jingham .
Wow @jingham you posted your comment and I landed the patch at the same time!
Jan 10 2020
Jan 9 2020
Jan 8 2020
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.
Apr 4 2019
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.
Mar 25 2019
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.
Feb 1 2019
@sgraenitz I've found an issue with this patch, using the Visual Studio 2015 generator.
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".
Sep 10 2018
Another issue:
Sep 7 2018
Added a test to TestAddressBreakpoints.py that sets an address breakpoint before launch, launches, and checks to see if the breakpoint was hit.
Yes, I'll add a new test to TestAddressBreakpoints.py.
Apr 20 2018
@JDevlieghere I'm seeing the same issue as @alberto_magni . The Visual Studio cmake generator gives errors. We're reverting it internally, but it needs to be fixed or reverted ASAP.
Feb 23 2018
Traditionally, remote gdbservers handle memory operations that overlap a software breakpoint. Writes get the new value saved off, and reads get the breakpoint opcode replaced by the saved value.
Jan 10 2018
Thanks for adding me, Pavel.
Oct 24 2017
We build lldb, clang and tools for Hexagon only, and call them hexagon-lldb, hexagon-clang, etc. The test infrastructure is smart enough to pick up hexagon-lldb-mi if we tell it to run with hexagon-lldb using --executable; will it be smart enough to run an in-tree hexagon-clang?
Oct 11 2017
Sep 20 2017
Sep 7 2017
Sep 6 2017
Tested with clang 3.8 on top-of-tree lldb-mi on Ubuntu 14.
Aug 31 2017
We want to go down into a pointer if it's the original parent, but not into a child that's a pointer. To avoid skipping children of a top-level pointer/reference, I think we need to do the type check in the loop.
Aug 30 2017
Updated with Greg's suggestion.
Added check for reference types, as Greg suggested.
Aug 25 2017
May 17 2017
Feb 3 2017
Oct 12 2016
I'm seeing the same issue as Nitesh, except in a different spot. The Hexagon Simulator doesn't support QSaveRegisterState, so lldb calls GDBRemoteRegisterContext::ReadAllRegisterValues. It gets a lock on the communication client, then calls ReadAllRegisters, which tries to get a lock on the communication client, and fails (hangs on Linux, crashes on Windows).
Sep 30 2016
The problem this scenario has is asynchronous output from 2 different sources. The original fix made Windows (or any lldb without libedit) much better, but I think most non-Windows builds will use libedit, because it's extremely useful. lldb-mi has a different set of constraints; the position of the prompt isn't as important, since users won't use it as a cue to tell when the debugger can accept more input.
Jun 23 2016
The Hexagon platform (currently in-house only) acts like the ios simulator platform, in that it doesn't connect - it fixes up the command line, then launches the Hexagon simulator (based on the debugserver launch code in the gdb-remote process plugin).