This is a known bug (bugzilla is slugish right now, so I can't look up
the number). The stopped event does not seem to get through most of
the times, although the stop is actually performed. I am afraid I
can't offer any workaround for the time being...
On 24 February 2016 at 07:36, Jeffrey.fudan
Makes sense, will file a bug for it.
Sent from my iPad
> On Feb 23, 2016, at 5:10 PM, Jim Ingham wrote:
>
> That also is a bug. If it is going to do a public stop, it has to send a
> stop event.
>
> Jim
>
>> On Feb 23, 2016, at 2:52 PM, Jeffrey Tan wrote:
>>
>> I am not sure. From the out
That also is a bug. If it is going to do a public stop, it has to send a stop
event.
Jim
> On Feb 23, 2016, at 2:52 PM, Jeffrey Tan wrote:
>
> I am not sure. From the output, it seems lldb does stop at the entry
> point(because you can issue "bt" command to dump the stack) in both
> platfor
I am not sure. From the output, it seems lldb does stop at the entry
point(because you can issue "bt" command to dump the stack) in both
platforms; the problem seems to be that it did not emit the stopped event
for its stop on linux.
On Tue, Feb 23, 2016 at 2:03 PM, Jim Ingham wrote:
> If the li
If the linux side is not obeying "stop_at_entry" then that is a bug.
Jim
> On Feb 23, 2016, at 1:49 PM, Jeffrey Tan via lldb-dev
> wrote:
>
> Hi,
>
> I have got lldb launch working fine on my macbook for sometime. But when I
> try the same code on Linux, it failed to emit any stopping event
Hi,
I have got lldb launch working fine on my macbook for sometime. But when I
try the same code on Linux, it failed to emit any stopping events during
initial launch.
When I run the reproduce code(listed at the end), I got the following
different results:
The key difference is that Macbook will