[lldb-dev] Difference of behaviour of process.Continue() between MacOSX and Linux
Pavel Labath via lldb-dev
lldb-dev at lists.llvm.org
Tue Sep 8 05:58:34 PDT 2015
thanks for your report.
Let me first ask you a question. Which version of lldb are you using?
If it's anything less than 3.7, then I strongly recommend to upgrade,
since linux support was not in a very good state there. If you are
using 3.7 or svn, then the thing you are describing should work. If it
does not please send your script along with your test app (or better
yet, file a bug at <llvm.org/bugs> and I will take a look.
On 8 September 2015 at 13:29, Louis Granboulan via lldb-dev
<lldb-dev at lists.llvm.org> wrote:
> Dear all,
> I am new to lldb-dev and I hope that this issue has not already been
> reported. I did not find any reference of it.
> I started with the example from section "Using the lldb.py module in python"
> and decided to have the process continue after having printed some
> information about the breakpoint context. It allows to have multiple
> breakpoints and display information about every breakpoint, or to have a
> breakpoint at a function that is called many times and to display
> information for every call.
> On a MacOSX machine (any recent version) it works well, but on a Linux
> machine (Ubuntu 14.04 64 bits) it looks like process.Continue() makes the
> program continue at the breakpoint instead of at the instruction following
> the breakpoint. Therefore, it enters an infinite loop.
> I can attach the python script, but this script is just made by taking the
> example of the webpage, putting in a "while True" loop everything after
> "state = process.GetState()" and adding at the end of the loop the
> instruction "process.Continue()".
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
More information about the lldb-dev