@lists.llvm.org
Subject: Re: [lldb-dev] Not able to set breakpoints above line #70 in lldb-mi.
The addresses for the two breakpoints are reported differently in your "break
list" output. The successful one is given as:
0x00013488
but the one that isn't sent is still given as:
MipsTest
of the order.
>
> I am on LLDB revision 279920, and LLVM revision 279925.
>
> Michael
>
> -Original Message-
> From: Greg Clayton [mailto:gclay...@apple.com]
> Sent: Tuesday, August 30, 2016 10:41 AM
> To: Michael Kuklinski
> Cc: lldb-dev@lists.llvm.
[mailto:gclay...@apple.com]
Sent: Tuesday, August 30, 2016 10:41 AM
To: Michael Kuklinski
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Not able to set breakpoints above line #70 in lldb-mi.
Seems to work for me just fine with your binary:
lldb /Volumes/work/gclayton/Downloads/MipsTest.bin
.@apple.com [mailto:jing...@apple.com]
Sent: Tuesday, August 30, 2016 11:04 AM
To: Michael Kuklinski
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Not able to set breakpoints above line #70 in lldb-mi.
"unresolved" means that we know what address we want to set a breakpoint at,
but
.@apple.com [mailto:jing...@apple.com]
Sent: Tuesday, August 30, 2016 11:04 AM
To: Michael Kuklinski
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Not able to set breakpoints above line #70 in lldb-mi.
"unresolved" means that we know what address we want to set a breakpoint at,
but
"unresolved" means that we know what address we want to set a breakpoint at,
but for some reason can't. For instance, if you were using -H and ran out of
hardware breakpoints, then the subsequent breakpoints would never get resolved,
since we can't implement them.
Anyway, going from unresolved
Seems to work for me just fine with your binary:
lldb /Volumes/work/gclayton/Downloads/MipsTest.bin
(lldb) target create "/Volumes/work/gclayton/Downloads/MipsTest.bin"
Current executable set to '/Volumes/work/gclayton/Downloads/MipsTest.bin'
(mipsr6el).
(lldb) break set -H -f Main.cpp -l 70
Brea
