[lldb-dev] Deleting lldb/utils/test/
Vedant Kumar via lldb-dev
lldb-dev at lists.llvm.org
Wed Oct 28 12:06:41 PDT 2020
Sounds good, deleted as of 158f3360.
> On Oct 27, 2020, at 10:46 AM, Jonas Devlieghere <jonas at devlieghere.com> wrote:
> Last time I looked at these nothing seemed relevant (anymore) to me either. I'm in favor of getting rid of the directory.
> On Tue, Oct 27, 2020 at 10:26 AM Vedant Kumar via lldb-dev <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>> wrote:
> I'm considering deleting the lldb/utils/test/ directory as a cleanup. Does anyone has a reason to keep these scripts around?
> Here are the files in the directory:
> % ls lldb/utils/test
> README-disasm README-run-until-faulted lldb-disasm.py main.c run-dis.py
> README-lldb-disasm disasm.py llvm-mc-shell.py ras.py run-until-faulted.py
> - disasm.py would've been helpful before lldb gained a 'disassemble' command, but it doesn't seem useful anymore
> - ditto for lldb-disasm.py; this one also seems quite Darwin-specific (I'm pretty sure it doesn't work anymore)
> - llvm-mc-shell.py might be useful if you want to type bytes by hand and see the disassembly, but even then, seems better to just do `echo "<bytes>" | llvm-mc`
> - ras.py isn't running the test suite properly, also (imo) seems like an ersatz Jenkins replacement
> - main.c is just an example program
> - run-dis.py looks like a driver for stress-testing lldb's disassembly command, but it looks very iOS/Darwin specific and has likely outlived its usefulness
> - run-until-faulted.py runs a program up to 100 times to see if any of the runs fail; I suspect most users would reach for a shell one-liner before looking for something like this script
> lldb-dev mailing list
> lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev <https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev