Hi! Can someone tell me what configure / build flags do you use when
building these packages (.tar.xz)? I guess there should be a script, but is
it available somewhere?
Thanks in advance,
- Ilia
On Mon, Oct 12, 2020 at 11:28 AM Diana Picus via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi,
>
>
Yep, it requires python from some time.
Guys, how you think is it okay to have such dependency for lldb-mi, or we
should try to get rid of this?
On Aug 17, 2017 21:11, "Ted Woodward" wrote:
Looking at the source, I think the failure is in
CMICmnLLDBDebugger::Initialize().
The snapshot is built
Hi!
Did you build it from sources? If yes, please provide your configure
options.
On Tue, Aug 15, 2017 at 7:10 PM, Eli Zaretskii via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Since at least two snapshots ago, lldb-mi no longer works on
> MS-Windows:
>
> D:\usr\archive>lldb-mi d:\usr\bin\ema
You are probably got it but yes, -file-list-exec-source-files and
-break-list commands are not implemented yet. I'll try to find the time to
fix it.
On Mon, Jul 31, 2017 at 9:44 PM, Eli Zaretskii via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> > From: "Ted Woodward"
> > Cc:
> > Date: Mon, 31 J
-llvm-dev
We support most MI commands and lldb-mi can be used alongside with Eclipse.
So probably it would work also with gdbgui. They are pretty compatible :)
On Tue, Mar 14, 2017 at 6:08 PM, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Not too much documentation unfortuna
Please check `-gdb-set target.async` option. Probably that's what you need.
On Thu, Feb 2, 2017 at 1:44 AM, Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Does lldb-mi support non-stop mode?
>
>
>
> If so, is there a way to set it besides “settings set target.non-stop-mode
> true”?
Hi!
I think it's okay that remote target is stopped when you connect to it.
Just skip it.
On Wed, Oct 19, 2016 at 8:14 AM, Chunseok Lee via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> I have noticed that lldb-mi stopped after executing "-target-select
> remote".
> My execution step is like:
> -
Hi!
Please see possible workarounds in
https://llvm.org/bugs/show_bug.cgi?id=28253.
On Tue, Sep 20, 2016 at 10:57 AM, Chunseok Lee via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Dear lldb dev team,
>
> I am working on running lldb-mi on arm32 device(like rpi) for remote
> debugging usage.
> Is
But what about SVN users? :)
Okay, I know format can be applied for modified fragments only. But why did
we leave some places unformatted? I thought "clang-format -i `find include
source tools -name '*.[cpp|h]'`" ends with empty diff.
On Thu, Sep 8, 2016 at 10:19 AM, Zachary Turner wrote:
> In o
Hi!
clang-formatting of my patch changed the style outside the patch (diff:
https://reviews.llvm.org/D24331?vs=70653&id=70654). Am I doing something
wrong?
On Wed, Sep 7, 2016 at 1:06 PM, Pavel Labath via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Windows unit tests passing now. All clear.
>
>
Hi Marc-Andre!
Ok, I'll review your patches. But if you have a couple of minutes, please
fill the bug form at llvm.org/bugs first.
On Mon, Jul 18, 2016 at 12:26 AM, Marc-Andre Laperle via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi,
>
> I am currently working on integrating LLDB-MI in Eclips
I'm not very familiar with Eclipse, so if there is a way to change start
sequence of MI commands, just remove "gdb-set target-async off" or replace
with "gdb-set target-async on". If not, then rebuild lldb-mi with
"disabled" target-async feature:
```
$ svn diff tools/lldb-mi/
Index: tools/lldb-mi/M
Hi Ted!
As noted in the copied code, *running is async notification and it only
must be shown in async mode. The test checks that it's not being shown in
sync mode. So the test is correct.
On Thu, May 19, 2016 at 12:56 AM, Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Packages/Py
Good point Greg! Eclipse turns on synchronous mode in lldb-mi but works as
if it's in async. I faced with that problem year and a half ago and I still
don't know why Eclipse does it. The last time, I forced lldb-mi to stay in
async mode and it was enough for me and Eclipse.
As for missing ^running
Hi!
Unfortunately, this is a regression introduced in r251082. From that moment
lldb-mi requires LLDB_DISABLE_PYTHON=0 for showing wide chars:
char16/char32 types.
If you cannot enable python support, I suggest you to:
1. ignore MI_add_summary's errors by returning TRUE:
```
Index: tools/lldb-mi/
On Fri, Sep 25, 2015 at 2:33 PM, Ilia K wrote:
> oops..
> -lldb-...@cs.uiuc.edu
> +lldb-dev@lists.llvm.org
>
> On Fri, Sep 25, 2015 at 2:30 PM, Hafiz Abid Qadeer
> wrote:
>
>> Sounds reasonable to me.
>>
>> On Fri, Sep 25, 2015 at 8:02 AM, Ilia K wrote:
>>
>>> Hi guys!
>>>
>>> I found the follo
16 matches
Mail list logo
