> On Sep 19, 2017, at 1:49 PM, Tatyana Krasnukha
> wrote:
>
>> -Original Message-
>> From: Greg Clayton [mailto:clayb...@gmail.com]
>> Sent: Tuesday, 19 September, 2017 9:48 PM
>> To: Tatyana Krasnukha
>> Cc: lldb-dev@lists.llvm.org
>> Subject: Re: [lldb-dev] How can lldb debug a remot
https://bugs.llvm.org/show_bug.cgi?id=34676
Adrian McCarthy changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |amcca...@google.com
--- Comment #1 from Adria
https://bugs.llvm.org/show_bug.cgi?id=34676
Bug ID: 34676
Summary: check-lldb target fails on Windows due to incomplete
compiler path
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
> -Original Message-
> From: Greg Clayton [mailto:clayb...@gmail.com]
> Sent: Tuesday, 19 September, 2017 9:48 PM
> To: Tatyana Krasnukha
> Cc: lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] How can lldb debug a remote bare-metal platform?
>
> So the problem is bare boards have no dyna
So the problem is bare boards have no dynamic loader. There is a
DynamicLoaderStatic which will load files at the address that they are
specified in the object files. When you load your ELF file using:
(lldb) file /path/to/foo.elf
What does:
(lldb) target list
show as the output? You might wa
Hello,
‘target modules load -lp’ fails with error “one or more section name + load
address pair must be specified”, works only with --slide option.
Another issue is that if breakpoint is set, Process::WriteMemory return zero
and ObjectFile::LoadInMemory interprets it as an error without setti
So you need to fix "DW_OP_call_frame_cfa" so it creates the same kind of value
on the expression stack as "DW_OP_reg31" does. I am guessing that "DW_OP_reg31"
will have a Value that whose value is "eValueTypeScalar". Verify this and
change "DW_OP_call_frame_cfa" to match. We want the Scalar gott
> -Original Message-
> From: Greg Clayton [mailto:clayb...@gmail.com]
> Sent: terça-feira, 19 de setembro de 2017 12:33
> To: Leonardo Bianconi
> Cc: lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] Reading eValueTypeLoadAddress with missing compiler
> type
>
>
> > On Sep 19, 2017, at
> On Sep 19, 2017, at 4:10 AM, Leonardo Bianconi
> wrote:
>
> Some more details:
>
> I'm part of the team that is working in LLDB to enable PPC64le architecture,
> so I'm running my test in a Power8 machine.
> When compiling the code with clang, it works, the issue happen when compiling
> wi
> On Sep 19, 2017, at 3:32 AM, Ramana wrote:
>
> Thank you so much Greg for your comments.
>
>> What architecture and os are you looking to support?
>
> The OS is Linux and the primary use scenario is remote debugging.
> Basically http://lists.llvm.org/pipermail/lldb-dev/2017-June/012445.html
Load like "target modules load" has a --load option that will load the ELF into
memory. I think it should do what you want. Let me know how it goes.
Greg Clayton
> On Sep 18, 2017, at 9:58 PM, cui bixiong wrote:
>
> Hi Greg:
>
> It's worked, thank you!, but I still have a question, in
Results from 'check-all' project:
-
Additional requirement: the regression tests requires the python 'psutil'
module.
There is a common error when trying to build 'check-all' project. One of
the instances can be seen on:
llvm\projects\compiler-rt\test\lit.
Some more details:
I'm part of the team that is working in LLDB to enable PPC64le architecture, so
I'm running my test in a Power8 machine.
When compiling the code with clang, it works, the issue happen when compiling
with gcc, which generates a different debug information content.
Talking a bi
Thank you so much Greg for your comments.
> What architecture and os are you looking to support?
The OS is Linux and the primary use scenario is remote debugging.
Basically http://lists.llvm.org/pipermail/lldb-dev/2017-June/012445.html
is what I am trying to achieve and unfortunately that query d
I have been trying to build LLDB on Windows (7) and after couple of days, I
managed to have a successfull build.
These are my findings:
1) Follow the instructions from
https://lldb.llvm.org/build.html
2) With Python 2.7, the cmake process fails, as it can't locate the
following files:
python_d
Thank you Ted for your comments.
On Mon, Sep 18, 2017 at 11:25 PM, Ted Woodward
wrote:
> I recently added Hexagon Linux support to lldb-server; I did what Greg
> suggested below - subclassed NativeRegisterContextLinux, like the other
> architectures did. I also added the software breakpoint opc
16 matches
Mail list logo
