- User Since
- Aug 14 2015, 10:30 PM (266 w, 5 d)
I agree it's nice to have somewhere, but git history should be fine. I should elaborate on motivations, 1. ensure everyone is using the script so that any issues are surfaced, 2. prevent missteps in the manual process, which may also be bit rotting if everyone is using the script.
Tue, Sep 22
Mon, Sep 21
Should lldb avoid calling asan (or any other sanitizer's) mmap? If so, maybe this function can be sanitizer aware and ignore those symbols.
Wed, Sep 16
Tue, Sep 15
Mon, Sep 14
Sun, Sep 13
Thu, Sep 10
for context this caused standalone swift-lldb builds to have warnings disabled via -w
@compnerd Saleem, what do you think? (see also my reply to you)
Wed, Sep 9
Tue, Sep 8
Add LLVM_ENABLE_WARNINGS to LLVMConfig.cmake.in
If another project defines LLVM_ENABLE_WARNINGS before loading HandleLLVMOptions, it seems correct to me that the first one is used. This change ensures the default value of ON is setup at the last possible opportunity, before LLVM_ENABLE_WARNINGS is read and acted on.
Follow up to 8aeb212887024a615ca02437cd12fa055bd54b6f
If an LLVM install disabled LLVM_ENABLE_WARNINGS, should other builds inherit that? I would think no, but is there a precedent for that that to be the case?
Mon, Sep 7
The LLVM_ENABLE_WARNINGS variable is read only within HandleLLVMOptions.cmake. Outside declarations/defaults have effect only when HandleLLVMOptions is loaded, one way or another.
@lebedev.ri clang/CMakeLists.txt contains include(HandleLLVMOptions) for its standalone build, I think this covers the issue you're pointing out
Thu, Sep 3
Given the expr status quo, I'd stick with that.
Wed, Sep 2
Tue, Sep 1
Thu, Aug 27
Wed, Aug 26
Aug 25 2020
Aug 24 2020
Dec 12 2019
Oct 25 2019
I wonder if it is time to take the gdb commands out and just make this a task -> lldb commands table?
fwiw I have a python command called abbrev that takes a command and shows you the alias you can use instead.
Thanks. I thought this was reasonable since the documentation shows many uses of lldb aliases already.
Oct 24 2019
Oct 10 2019
Jul 9 2019
May 9 2019
Apr 4 2019
Sounds good @aprantl
Apr 3 2019
Remove unintended changes.
Mar 10 2019
Thanks for reviewing @clayborg.
I'm getting build failures that appear to be caused by this patch. I'm compiling on macOS with Xcode 10.1. The failures are uses of LLDB_RECORD_DUMMY(), passing a callback function pointer as one of the args. This results in errors like:
Feb 27 2019
@clayborg this has been updated the approach you suggested, adding an interactive parameter.
Feb 16 2019
Add interactive parameter
Feb 15 2019
Jan 18 2019
Nov 27 2018
@compnerd would you be willing to accept?
@jingham If you're still willing to review this change to command regex, it is updated per our previous discussion, thanks.
Nov 4 2018
@keith I screwed up and committed without amending the commit message to attribute you as the author :( – I'm sorry
Nov 3 2018
There are other commands that print instructions in the same way that command regex does, should they be updated in this change too?