On Mon, Jul 25, 2016 at 4:46 PM, Greg Clayton wrote:
> I am glad to hear this. We will be happy to help with any issues you run
into.
Thanks!
> If you have examples for any issues you run into, it would be great to
get MI text snippets that we can run through the lldb-mi program on our
end, it c
I am glad to hear this. We will be happy to help with any issues you run into.
If you have examples for any issues you run into, it would be great to get MI
text snippets that we can run through the lldb-mi program on our end, it can
help us to understand and reproduce any issues you run into.
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
Hi,
I am currently working on integrating LLDB-MI in Eclipse CDT so that
it works more or less out of the box in the next CDT release due in
September (setting the lldb-mi path automatically, etc). For this
specific issue, I made it so that it simply does not send the
target-async command from Ecl
Thanks Ilia.
For now I check running Eclipse commands manually by changing to "gdb-set
target-async *on*" and it solves the issue for manual run. I will try to
find out how to change these commands in eclipse otherwise I will rebuild
lldvmi. I will keep you posted...
--
Have a nice day!
Regards
uot;,func="test_main_start",file="downscaleBy2.c",fullname="C:\installSDK\Hexagon_SDK\3.0\examples\common\downscaleBy2\src/downscaleBy2.c",line="96",pending=["downscaleBy2.c:96"],times="0",original-location="downscaleBy2.c:96"}
RX:(gd
tml talks about what
> this command does. It gives a list of process groups that the debugger is
> debugging, so it doesn’t matter if a certain process is running or not.
>
>
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center
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
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
From the sample I see that LLDB is in synchronous mode. It was caused by:
> 313,449 12-gdb-set target-async off
> 313,453 12^done
This sets LLDB into synchronous mode where if you say "-exec-continue", that
command won't return until the target stops. This causes lldb-mi to not process
any comm
Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
From: dipt...@gmail.com [mailto:dipt...@gmail.com]
Sent: Friday, July 08, 2016 6:23 AM
To: Ted Woodward
Cc: Greg Clayton ; LLDB
Subject: Re: [lldb-dev] LLDB-MI from Eclipse hangs
Thanks Ted for your
Thanks Greg. But is it possible that for eclipse support some new wrapper
command is added ? [
https://www.codeplay.com/portal/lldb-mi-driver---part-4-how-to-add-a-command]
Not sure, just a thought. I am googling to see more details but not much
luck yet.
Attached is lldb-mi sample. Please let me
Thanks Greg. Attached is the file after sampling lldb-mi. Please let me
know if you can find some clue from it.
--
Have a nice day!
Regards,
Dipti
On Fri, Jul 8, 2016 at 5:49 AM, Greg Clayton wrote:
> It looks like we continue and then ask fore thread groups? I am not sure
> on the rules of M
Actually you should have seen a ^running as a response from -exec-continue:
-exec-continue
^running
(gdb)
But we don't see that here.
Also, -exec-continue doesn't believe it takes any arguments in the lldb-mi.
Check the tools/lldb-mi/MICmdCmdExec.cpp source file in the LLDB sources. Note
that
It looks like we continue and then ask fore thread groups? I am not sure on the
rules of MI. Can you ask another question before receiving a response? If we
say command 18 is "-exec-continue --thread-group i1", can you send command 19
without receiving a response?
314,372 18-exec-continue --thr
Thanks Greg for your reply.
Attached below is the GDB trace, please let me know if it helps in any ways.
It would be helpful if you can tell me on how to capture (I am really new
to lldb, sorry for bothering you):
- sample lldb-mi to see what it is doing.
- complete packet log of the traffic betw
You should sample lldb-mi to see what it is doing. Also if you can get a more
complete packet log of the traffic between Eclipse and lldb-mi we might be able
to see what is going on. Another thing to note: if you are remote debugging to
a Mac from another machine and don't have any files cached
17 matches
Mail list logo
