Hi guys,
Any suggestions on the following?
I've got some scripts written for gdb's Python API, and I'm trying to
port them to LLDB. Those script include some code that ideally
executes during, or shortly after, each completed call to a particular
function. I.e., the user says he/she is interest
Hi Pavel,
Would it make sense to address this problem by fixing clang-format,
rather than working around it?
(Assuming the clang-format fix is relatively easy, and acceptable to
clang-format's maintainers.)
- Christian
On Thu, Aug 11, 2016 at 10:41 AM, Pavel Labath via lldb-dev
wrote:
> I just
On Thu, Aug 11, 2016 at 11:18 AM, Adrian McCarthy wrote:
> I assume Christian Convey was referring to clang-format moving the
> "//breakpoint here" comments in the tests to different lines.
That's correct. I apologize for the confusion.
- Christian
__
Hi guys,
I'm trying to use watchpoints to detect user-space reads/writes of an
arbitrary C/C++ program variable.
For example:
void foo() {
int x; // <-- I'm interested in 'x'
x = 10; // <-- I want to detect this
for (int i = 0; i < 4; ++i) {
x = i; // <-- And th
Hi Greg,
>>
>> Does anyone know of a way to minimize or eliminate this problem?
>
> Just take the address of your variable at some point in your code and it will
> force it into memory.
Thanks for your idea. I can see why taking the variable's address (in
an expression that's not optimized awa
