[lldb-dev] How to preserve command history?

2020-04-20 Thread Andrzej Warzynski via lldb-dev 

Hello,

I've just tried using lldb on Ubuntu* and I couldn't get the command
history to work. More specifically, the command history was not
preserved between the sessions. IIUC, one has to create the lldb-history
file for this to work:

mkdir -p ~/.lldb/
touch ~/.lldb/lldb-history

This is rather non-obvious and AFAIK undocumented solution (and very
different to what's required with GDB).

Is there a better way to achieve this? Would it make sense to update the
docs with this information (e.g.
https://lldb.llvm.org/man/lldb.html#configuration-files)? I'm happy to
submit a patch.

Thanks,
-Andrzej

* lldb-8 on Ubuntu 16.04
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] How to preserve command history?

2020-04-20 Thread Andrzej Warzynski via lldb-dev 

Cheers for your quick reply! You're probably referring to this:

https://github.com/llvm/llvm-project/blob/01bcc3e9371470e1974f066ced353df15e10056d/lldb/source/Host/common/Editline.cpp#L216

That's a fairly recent change so that explains why it didn't work for me
with lldb-8. I've also checked lldb-10 on Arch and that indeed works
out-of-the-box. Guess I need to make sure I always use the latest and
greatest.

-Andrzej

On 20/04/2020 15:39, Raphael “Teemperor” Isemann wrote:

LLDB is explicitly creating the .lldb directory for the user (see Editline.cpp 
-> GetHistoryFilePath). Is this also happening in a more recent LLDB version? 
It’s working for me on the latest release on Arch.


On Apr 20, 2020, at 4:34 PM, Andrzej Warzynski via lldb-dev 
 wrote:

Hello,

I've just tried using lldb on Ubuntu* and I couldn't get the command
history to work. More specifically, the command history was not
preserved between the sessions. IIUC, one has to create the lldb-history
file for this to work:

mkdir -p ~/.lldb/
touch ~/.lldb/lldb-history

This is rather non-obvious and AFAIK undocumented solution (and very
different to what's required with GDB).

Is there a better way to achieve this? Would it make sense to update the
docs with this information (e.g.
https://lldb.llvm.org/man/lldb.html#configuration-files)? I'm happy to
submit a patch.

Thanks,
-Andrzej

* lldb-8 on Ubuntu 16.04
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev



IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Openmp-dev] [Release-testers] 13.0.0-rc3 has been tagged

2021-09-20 Thread Andrzej Warzynski via lldb-dev 

Hi Brian,

Thank you for helping with the release!

On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote:
I also disabled flang (-no-flang) because of 
memory exhaustion while trying to build.  Is this increased memory 
consumption expected or could it be a bug?


The memory usage of LLVM Flang was discussed in the past:
* https://bugs.llvm.org/show_bug.cgi?id=50059
* https://lists.llvm.org/pipermail/flang-dev/2019-November/61.html

It's not great, but sadly it is rather unlikely to improve in the near 
future.


Thanks,
-Andrzej



$ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967 
  clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz


On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers 
mailto:release-test...@lists.llvm.org>> 
wrote:


Hi,

I've tagged 13.0.0-rc3.  This will likely be the last rc unless
there are
critical bugs that are found.  Please test the release and report
results.

-Tom

___
Release-testers mailing list
release-test...@lists.llvm.org 
https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers




--
-Brian

___
Openmp-dev mailing list
openmp-...@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev


___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Openmp-dev] [Release-testers] 13.0.0-rc3 has been tagged

2021-09-20 Thread Andrzej Warzynski via lldb-dev 


On 20/09/2021 19:53, Brian Cain wrote:


Is there a way to set some kind of variable to 
limit the concurrency for building (only) these targets?  Like 
LLVM_PARALLEL_LINK_JOBS works today.  


AFAIK, that's not possible ATM. I agree that it would be a good 
workaround and we should look into this. But it will be tricky to get 
this in on time for Release 13.


I suspect that you are already using either ld.gold or lld? Perhaps you 
could build all of LLVM with LLVM_PARALLEL_COMPILE_JOBS=1 (or some other 
small value)?



-Andrzej

What if test-release.sh defined
LLVM_PARALLEL_FLANG_COMPILE_JOBS to "1" (or I defined it in 
-configure-flags) and there were some cmake magic that handled that 
input to control how the build were invoked?  I think that would be a 
good workaround.


Thanks,
-Andrzej

 >
 > $ cat
clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256
 > 488ff13c9a54f6b7b2aeb26e930da7d72e32a15542929cd642fc0b7d37e79967
 >   clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz
 >
 > On Mon, Sep 13, 2021 at 11:40 PM Tom Stellard via Release-testers
 > mailto:release-test...@lists.llvm.org>
>>
 > wrote:
 >
 >     Hi,
 >
 >     I've tagged 13.0.0-rc3.  This will likely be the last rc unless
 >     there are
 >     critical bugs that are found.  Please test the release and report
 >     results.
 >
 >     -Tom
 >
 >     ___
 >     Release-testers mailing list
 > release-test...@lists.llvm.org

>
 > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

 >   
  >
 >
 >
 >
 > --
 > -Brian
 >
 > ___
 > Openmp-dev mailing list
 > openmp-...@lists.llvm.org 
 > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev

 >



--
-Brian

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev