Negative breakpoint ID’s are used for breakpoints lldb sets for internal purposes. You can see the internal breakpoints with the “break list -i” command.
“continue” doesn’t usually need to set internal breakpoints, however. And we don’t usually tell you about internal breakpoint hits, especially if you hit a user breakpoint at the same time. So that is a little curious. But I also wonder if you are hitting this breakpoint over and over? What is the hit count on breakpoint 3? You can see this in the output of “break list 3.1" Jim > On Nov 16, 2017, at 6:20 PM, Jian Liu/Gmail via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > > Dear all, > > I have just debug KLEE with lldb. A breakpoint was set on the function > "executeAllocUnbounded". After the breakpoint was hiited, I used "continue" > to let the program to go on. However, it did not work. The respose from lldb > is following: > > (lldb) > Process 10254 stopped > * thread #1, name = 'klee', stop reason = breakpoint 3.1 -1364.1 > frame #0: > klee`klee::Executor::executeAllocUnbounded(this=0x0000000001278800, > state=0x000000000132d710, size=4, target=0x000000000134ef00) at > Executor.cpp:3036 > > NOTE that, there is a negative number "-1364.1" showed in stop reason. When I > hit "continue" again, the number was change to "-1366.1", by mius -2 > > I want to know what is the mean of "-1364.1" here. How to let the program to > continue. Thanks. > > --- > Jian Liu > > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
