[lldb-dev] multiple NameErrors on lldb startup, doesn't seem to affect lldb performance
Here is what happens: prowat% lldb modTS (lldb) target create "modTS" Traceback (most recent call last): File "", line 1, in File "/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Resources/Python/lldb/__init__.py", line 98, in import six ImportError: No module named six Traceback (most recent call last): File "", line 1, in NameError: name 'run_one_line' is not defined Traceback (most recent call last): File "", line 1, in NameError: name 'run_one_line' is not defined Traceback (most recent call last): File "", line 1, in NameError: name 'run_one_line' is not defined Traceback (most recent call last): .. .. .. (at least 100 repetitions) .. .. .. Traceback (most recent call last): File "", line 1, in NameError: name 'run_one_line' is not defined Current executable set to 'modTS' (x86_64). (lldb) === Exactly the same output appears when lldb is started by: == (lldb) process attach -n modTS == prowat% lldb -v lldb-902.0.79.7 Swift-4.1 === This is a nuisance but LLDB is still usable. OSX 10.13 Peter ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] Unsubscribe “pro...@ucsd.edu”
Thank you ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] How to debug a child process ?
I have a process P1 that forks a child process P2. Both have graphic displays, P2 is an animation depending on data from P1. P2 suddenly disappears at a time that is never the same as any previous run. I use lldb to run P1 and when P2 disappears P1 hangs, and lldb prints a message like "2019-09-30 16:19:18.648148-0700 animTS[54508:1706244] detected buffer overflow”. animTS is my process P2, 54508 is the P2 process number. What is the number 1706244 ? It isn’t an address. How can I run lldb on the P2 process ? Thanks for any help. — Peter R ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] printf works under lldb but not otherwise
I have a simple C program that has printf statements. It produces zero output. However when it’s run under lldb, it prints correct output. How could this be? I tried replacing the printf statements by “fprintf” to a file: same behaviour - no file created and no output, but under lldb, the file is created with correct output data. Peter R ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
