I am running a Swift built binary in lldb.
In ~/.lldbinit I have:
command script import ~/dev/lldbscripts/ignore_signals.py
I execute lldb from an sh script with:
exec lldb .build_run/x86_64-unknown-linux-gnu/debug/MyModelApp
run to start executing my process inside lldb.
I am experiencing meteoric disk usage increase during the run, this is a 400GB drive:
It turns out this is a file
/tmp/reproducer-337129/sbapi.bin swelling in size. The lldb docs on reproducers indicate that I would need to run
lldb --collect to enable reproducers. I've never passed
--collect to LLDB, I didn't know it was an option. Does anyone know why LLDB is collecting this data anyway? Is there a debug switch somewhere else, or is it turned on by default because I am using a
command script? I'm not expecting LLDB to crash and would prefer to disable the reproducers collection. I'm using the lldb that ships with Swift for Tensorflow on Ubuntu 18.04:
$ which lldb /home/xander/swift-tensorflow-RELEASE-0.10-cuda10.2-cudnn7-ubuntu18.04/usr/bin/lldb $ lldb --version lldb version 10.0.0 (https://github.com/apple/llvm-project.git revision 55d27a5828841a530b402bbe17df84580115065e) Swift version 5.3-dev (LLVM 55d27a5828, Swift 6a5d84ec08)
But I'm not aware that Swift for Tensorflow makes lldb modifications?
Apologies if this isn't the best place to be asking LLDB usage questions, please let me know if there's a better place for it.