[lldb-dev] [Bug 21142] test_with_dwarf_and_run_command (TestInlinedBreakpoints.InlinedBreakpointsTestCase) failing on FreeBSD 10.1

2015-09-16 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=21142

ema...@freebsd.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from ema...@freebsd.org ---
Decorator removed in revision 247800.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [Bug 18832] Three watchpoint set expression tests fail on FreeBSD

2015-09-16 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=18832

ema...@freebsd.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from ema...@freebsd.org ---
Decorators removed in revision 247801.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [Bug 24843] New: "ninja lldb-server" on OS X reports "error: unknown target 'lldb-server'"

2015-09-16 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=24843

Bug ID: 24843
   Summary: "ninja lldb-server" on OS X reports "error: unknown
target 'lldb-server'"
   Product: lldb
   Version: unspecified
  Hardware: Macintosh
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: todd.fi...@gmail.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [Bug 24846] New: test runner: multiprocessing test runner sometimes halting after "hangup"

2015-09-16 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=24846

Bug ID: 24846
   Summary: test runner: multiprocessing test runner sometimes
halting after "hangup"
   Product: lldb
   Version: unspecified
  Hardware: Macintosh
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: todd.fi...@gmail.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

154 out of 300 test suites processed - TestInferiorCrashing.py
[2]20486 hangup lldb/test/dotest.py --executable {...} |

And then it quits the whole test suite.

Figure out what's happening here and make sure it doesn't take down the whole
test suite run.  I have another change I started last night to deal with
signal-based dotest inferior issues, which might cover this.  This is looking
like something got a SIGHUP (?).  The timeout command being used kills the
process with a SIGQUIT, so I don't think this is due to the timeout command.

I'm seeing this on OS X with the following test runners:
default test runner (multiprocessing)
threading

I'm not seeing it on the multiprocessing-pool or threading-pool test runners.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] SBTarget::AttachToProcessWithID hangs

2015-09-16 Thread Philippe Lavoie via lldb-dev

I am trying to attach to a stopped process on our dsp target using the SBTarget 
interface but the call hangs.
What I understand is that it is waiting for events on the "lldb.process" 
broadcaster using the "lldb.Target.Attach.attach.hijack" listener.

Enabling the logs, I see that the process is attached successfully and that the 
stop event is generated. It just seems that the event is not seen by the 
listener.

1442428969.32100 004B9590 Listener::WaitForEventsInternal (timeout = { 
 }) for lldb.Target.Attach.attach.hijack
1442428969.32100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
(event_sp = {00A72050 Event: broadcaster = 004BC7F4 (opus.remote), type = 
0x0001, data = }, unique =0) hijack = 
1442428969.34100 0049AC50 Broadcaster("lldb.target")::BroadcastEvent 
(event_sp = {00A70C78 Event: broadcaster = 0049AC50 (lldb.target), type = 
0x0002 (modules-loaded), data = {}}, unique =0) hijack = 
1442428969.34100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
(event_sp = {00A723C8 Event: broadcaster = 004BC7F4 (opus.remote), type = 
0x0001, data = }, unique =0) hijack = 
1442428969.45000 004BC394 
Broadcaster("lldb.process.internal_state_broadcaster")::BroadcastEvent 
(event_sp = {00A723C8 Event: broadcaster = 004BC394 
(lldb.process.internal_state_broadcaster), type = 0x0001, data = { process 
= 004BC308 (pid = 1), state = stopped}}, unique =0) hijack = 
1442428969.45200 004BC42C 
Listener('lldb.process.internal_state_listener')::AddEvent (event_sp = 
{00A723C8})
1442428969.45300 031CF700 Listener::WaitForEventsInternal (timeout = { 
 }) for ProcessOpusRemote::AsyncThread
1442428969.45300 004BC42C 'lldb.process.internal_state_listener' 
Listener::FindNextEventInternal(broadcaster=, 
broadcaster_names=[0], event_type_mask=0x, remove=1) event 
00A723C8
1442428969.45900 0309F8D4 Listener::StartListeningForEvents (broadcaster = 
004BC5F4, mask = 0x0020) acquired_mask = 0x0020 for 
Communication::SyncronizeWithReadThread
1442428969.47000 Process::ShouldBroadcastEvent (00A723C8) => new state: 
stopped, last broadcast state: stopped - YES
1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
(event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
stopped}}, unique =0) hijack = 
1442428969.47300 00402598 Listener('lldb.Debugger')::AddEvent (event_sp = 
{00A723C8})
1442428969.47400 004BC42C Listener::WaitForEventsInternal (timeout = { 
 }) for lldb.process.internal_state_listener

Here's the code I use to attach.

SBDebugger::Initialize();

SBDebugger debugger = lldb::SBDebugger::Create(false);
debugger.SetAsync(true);

const char* categories [] = { "process", "events", 0 };
if (!debugger.EnableLog("lldb", categories))
return -1;

pid_t pid = 1;

SBTarget target = debugger.CreateTargetWithFileAndArch(elffile_name, "opus2");

SBError error;
SBListener listener("test_listener");

SBProcess process = target.AttachToProcessWithID(listener, pid, error);

if (!process.IsValid())
{
   ...


I would be grateful for any insight on the cause of this behavior.

Thanks,
-Philippe
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

2015-09-16 Thread Jim Ingham via lldb-dev
Did you try waiting for an event on the listener you've passed to 
AttachToProcess?  The last event after everything is done should be the 
notification to the public listener (i.e. your test_listener) that the process 
you attached to has stopped, and nobody is fetching that.

Jim

> On Sep 16, 2015, at 11:59 AM, Philippe Lavoie via lldb-dev 
>  wrote:
> 
> 
> I am trying to attach to a stopped process on our dsp target using the 
> SBTarget interface but the call hangs. 
> What I understand is that it is waiting for events on the "lldb.process" 
> broadcaster using the "lldb.Target.Attach.attach.hijack" listener.
> 
> Enabling the logs, I see that the process is attached successfully and that 
> the stop event is generated. It just seems that the event is not seen by the 
> listener.
> 
> 1442428969.32100 004B9590 Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.Target.Attach.attach.hijack
> 1442428969.32100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A72050 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.34100 0049AC50 Broadcaster("lldb.target")::BroadcastEvent 
> (event_sp = {00A70C78 Event: broadcaster = 0049AC50 (lldb.target), type = 
> 0x0002 (modules-loaded), data = {}}, unique =0) hijack = 
> 1442428969.34100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.45000 004BC394 
> Broadcaster("lldb.process.internal_state_broadcaster")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC394 
> (lldb.process.internal_state_broadcaster), type = 0x0001, data = { 
> process = 004BC308 (pid = 1), state = stopped}}, unique =0) hijack = 
> 1442428969.45200 004BC42C 
> Listener('lldb.process.internal_state_listener')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.45300 031CF700 Listener::WaitForEventsInternal (timeout = { 
>  }) for ProcessOpusRemote::AsyncThread
> 1442428969.45300 004BC42C 'lldb.process.internal_state_listener' 
> Listener::FindNextEventInternal(broadcaster=, 
> broadcaster_names=[0], event_type_mask=0x, remove=1) event 
> 00A723C8
> 1442428969.45900 0309F8D4 Listener::StartListeningForEvents (broadcaster 
> = 004BC5F4, mask = 0x0020) acquired_mask = 0x0020 for 
> Communication::SyncronizeWithReadThread
> 1442428969.47000 Process::ShouldBroadcastEvent (00A723C8) => new state: 
> stopped, last broadcast state: stopped - YES
> 1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
> 0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
> stopped}}, unique =0) hijack = 
> 1442428969.47300 00402598 Listener('lldb.Debugger')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.47400 004BC42C Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.process.internal_state_listener
> 
> Here's the code I use to attach.
> 
> SBDebugger::Initialize();
> 
> SBDebugger debugger = lldb::SBDebugger::Create(false);
> debugger.SetAsync(true);
> 
> const char* categories [] = { "process", "events", 0 };
> if (!debugger.EnableLog("lldb", categories))
> return -1;
> 
> pid_t pid = 1;
> 
> SBTarget target = debugger.CreateTargetWithFileAndArch(elffile_name, "opus2");
> 
> SBError error;
> SBListener listener("test_listener");
> 
> SBProcess process = target.AttachToProcessWithID(listener, pid, error);
> 
> if (!process.IsValid())
> {
>...
> 
> 
> I would be grateful for any insight on the cause of this behavior.
> 
> Thanks,
> -Philippe
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

2015-09-16 Thread Greg Clayton via lldb-dev
A few questions:

Which process plug-in does your debugging target use? 
Is it a GDB Remote based debug session? 
   If so is it using lldb-server? 
   a custom GDB server?

In general, we expect to receive a eStateStopped process event if the attach is 
successful and this is what we are waiting for. If you have a custom Process 
subclass, you will need to make sure you stop your target and broadcast a 
eStateStopped event. If you are using GDB remote, please enable logging with 
the following line before calling AttachToProcessWithID:

debugger.HandleCommand("log enable -f /tmp/packets.txt gdb-remote packets");

Then run and watch things fail, and attach the log.

Greg Clayton

> On Sep 16, 2015, at 11:59 AM, Philippe Lavoie via lldb-dev 
>  wrote:
> 
> 
> I am trying to attach to a stopped process on our dsp target using the 
> SBTarget interface but the call hangs. 
> What I understand is that it is waiting for events on the "lldb.process" 
> broadcaster using the "lldb.Target.Attach.attach.hijack" listener.
> 
> Enabling the logs, I see that the process is attached successfully and that 
> the stop event is generated. It just seems that the event is not seen by the 
> listener.
> 
> 1442428969.32100 004B9590 Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.Target.Attach.attach.hijack
> 1442428969.32100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A72050 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.34100 0049AC50 Broadcaster("lldb.target")::BroadcastEvent 
> (event_sp = {00A70C78 Event: broadcaster = 0049AC50 (lldb.target), type = 
> 0x0002 (modules-loaded), data = {}}, unique =0) hijack = 
> 1442428969.34100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.45000 004BC394 
> Broadcaster("lldb.process.internal_state_broadcaster")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC394 
> (lldb.process.internal_state_broadcaster), type = 0x0001, data = { 
> process = 004BC308 (pid = 1), state = stopped}}, unique =0) hijack = 
> 1442428969.45200 004BC42C 
> Listener('lldb.process.internal_state_listener')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.45300 031CF700 Listener::WaitForEventsInternal (timeout = { 
>  }) for ProcessOpusRemote::AsyncThread
> 1442428969.45300 004BC42C 'lldb.process.internal_state_listener' 
> Listener::FindNextEventInternal(broadcaster=, 
> broadcaster_names=[0], event_type_mask=0x, remove=1) event 
> 00A723C8
> 1442428969.45900 0309F8D4 Listener::StartListeningForEvents (broadcaster 
> = 004BC5F4, mask = 0x0020) acquired_mask = 0x0020 for 
> Communication::SyncronizeWithReadThread
> 1442428969.47000 Process::ShouldBroadcastEvent (00A723C8) => new state: 
> stopped, last broadcast state: stopped - YES
> 1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
> 0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
> stopped}}, unique =0) hijack = 
> 1442428969.47300 00402598 Listener('lldb.Debugger')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.47400 004BC42C Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.process.internal_state_listener
> 
> Here's the code I use to attach.
> 
> SBDebugger::Initialize();
> 
> SBDebugger debugger = lldb::SBDebugger::Create(false);
> debugger.SetAsync(true);
> 
> const char* categories [] = { "process", "events", 0 };
> if (!debugger.EnableLog("lldb", categories))
> return -1;
> 
> pid_t pid = 1;
> 
> SBTarget target = debugger.CreateTargetWithFileAndArch(elffile_name, "opus2");
> 
> SBError error;
> SBListener listener("test_listener");
> 
> SBProcess process = target.AttachToProcessWithID(listener, pid, error);
> 
> if (!process.IsValid())
> {
>...
> 
> 
> I would be grateful for any insight on the cause of this behavior.
> 
> Thanks,
> -Philippe
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

2015-09-16 Thread Philippe Lavoie via lldb-dev

It is a custom process plug-in using a proprietary protocol to communicate with 
the debug target.

In the process plugin's AsyncThread, I set the process private state to 
eStateStopped by calling process->SetPrivateState.
Is it enough to broadcast the state change?

The event is in the events log:

> 1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
> 0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
> stopped}}, unique =0) hijack = 

-Philippe

From: Greg Clayton [gclay...@apple.com]
Sent: Wednesday, September 16, 2015 3:36 PM
To: Philippe Lavoie
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

A few questions:

Which process plug-in does your debugging target use?
Is it a GDB Remote based debug session?
   If so is it using lldb-server?
   a custom GDB server?

In general, we expect to receive a eStateStopped process event if the attach is 
successful and this is what we are waiting for. If you have a custom Process 
subclass, you will need to make sure you stop your target and broadcast a 
eStateStopped event. If you are using GDB remote, please enable logging with 
the following line before calling AttachToProcessWithID:

debugger.HandleCommand("log enable -f /tmp/packets.txt gdb-remote packets");

Then run and watch things fail, and attach the log.

Greg Clayton

> On Sep 16, 2015, at 11:59 AM, Philippe Lavoie via lldb-dev 
>  wrote:
>
>
> I am trying to attach to a stopped process on our dsp target using the 
> SBTarget interface but the call hangs.
> What I understand is that it is waiting for events on the "lldb.process" 
> broadcaster using the "lldb.Target.Attach.attach.hijack" listener.
>
> Enabling the logs, I see that the process is attached successfully and that 
> the stop event is generated. It just seems that the event is not seen by the 
> listener.
>
> 1442428969.32100 004B9590 Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.Target.Attach.attach.hijack
> 1442428969.32100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A72050 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.34100 0049AC50 Broadcaster("lldb.target")::BroadcastEvent 
> (event_sp = {00A70C78 Event: broadcaster = 0049AC50 (lldb.target), type = 
> 0x0002 (modules-loaded), data = {}}, unique =0) hijack = 
> 1442428969.34100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.45000 004BC394 
> Broadcaster("lldb.process.internal_state_broadcaster")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC394 
> (lldb.process.internal_state_broadcaster), type = 0x0001, data = { 
> process = 004BC308 (pid = 1), state = stopped}}, unique =0) hijack = 
> 1442428969.45200 004BC42C 
> Listener('lldb.process.internal_state_listener')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.45300 031CF700 Listener::WaitForEventsInternal (timeout = { 
>  }) for ProcessOpusRemote::AsyncThread
> 1442428969.45300 004BC42C 'lldb.process.internal_state_listener' 
> Listener::FindNextEventInternal(broadcaster=, 
> broadcaster_names=[0], event_type_mask=0x, remove=1) event 
> 00A723C8
> 1442428969.45900 0309F8D4 Listener::StartListeningForEvents (broadcaster 
> = 004BC5F4, mask = 0x0020) acquired_mask = 0x0020 for 
> Communication::SyncronizeWithReadThread
> 1442428969.47000 Process::ShouldBroadcastEvent (00A723C8) => new state: 
> stopped, last broadcast state: stopped - YES
> 1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
> 0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
> stopped}}, unique =0) hijack = 
> 1442428969.47300 00402598 Listener('lldb.Debugger')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.47400 004BC42C Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.process.internal_state_listener
>
> Here's the code I use to attach.
>
> SBDebugger::Initialize();
>
> SBDebugger debugger = lldb::SBDebugger::Create(false);
> debugger.SetAsync(true);
>
> const char* categories [] = { "process", "events", 0 };
> if (!debugger.EnableLog("lldb", categories))
> return -1;
>
> pid_t pid = 1;
>
> SBTarget target = debugger.CreateTargetWithFileAndArch(elffile_name, "opus2");
>
> SBError error;
> SBListener listener("test_listener");
>
> SBProcess process = target.AttachToProcessWithID(listener, pid, error);
>
> if (!process.IsValid())
> {
>...
>
>
> I would be grateful for any insight on the cause of this b

Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

2015-09-16 Thread Philippe Lavoie via lldb-dev
It is the AttachToProcessWithID that hangs and never returns, so I cannot use 
my listener yet.

-Philippe

From: jing...@apple.com [jing...@apple.com]
Sent: Wednesday, September 16, 2015 3:34 PM
To: Philippe Lavoie
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] SBTarget::AttachToProcessWithID hangs

Did you try waiting for an event on the listener you've passed to 
AttachToProcess?  The last event after everything is done should be the 
notification to the public listener (i.e. your test_listener) that the process 
you attached to has stopped, and nobody is fetching that.

Jim

> On Sep 16, 2015, at 11:59 AM, Philippe Lavoie via lldb-dev 
>  wrote:
>
>
> I am trying to attach to a stopped process on our dsp target using the 
> SBTarget interface but the call hangs.
> What I understand is that it is waiting for events on the "lldb.process" 
> broadcaster using the "lldb.Target.Attach.attach.hijack" listener.
>
> Enabling the logs, I see that the process is attached successfully and that 
> the stop event is generated. It just seems that the event is not seen by the 
> listener.
>
> 1442428969.32100 004B9590 Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.Target.Attach.attach.hijack
> 1442428969.32100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A72050 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.34100 0049AC50 Broadcaster("lldb.target")::BroadcastEvent 
> (event_sp = {00A70C78 Event: broadcaster = 0049AC50 (lldb.target), type = 
> 0x0002 (modules-loaded), data = {}}, unique =0) hijack = 
> 1442428969.34100 004BC7F4 Broadcaster("opus.remote")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC7F4 (opus.remote), type = 
> 0x0001, data = }, unique =0) hijack = 
> 1442428969.45000 004BC394 
> Broadcaster("lldb.process.internal_state_broadcaster")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC394 
> (lldb.process.internal_state_broadcaster), type = 0x0001, data = { 
> process = 004BC308 (pid = 1), state = stopped}}, unique =0) hijack = 
> 1442428969.45200 004BC42C 
> Listener('lldb.process.internal_state_listener')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.45300 031CF700 Listener::WaitForEventsInternal (timeout = { 
>  }) for ProcessOpusRemote::AsyncThread
> 1442428969.45300 004BC42C 'lldb.process.internal_state_listener' 
> Listener::FindNextEventInternal(broadcaster=, 
> broadcaster_names=[0], event_type_mask=0x, remove=1) event 
> 00A723C8
> 1442428969.45900 0309F8D4 Listener::StartListeningForEvents (broadcaster 
> = 004BC5F4, mask = 0x0020) acquired_mask = 0x0020 for 
> Communication::SyncronizeWithReadThread
> 1442428969.47000 Process::ShouldBroadcastEvent (00A723C8) => new state: 
> stopped, last broadcast state: stopped - YES
> 1442428969.47100 004BC318 Broadcaster("lldb.process")::BroadcastEvent 
> (event_sp = {00A723C8 Event: broadcaster = 004BC318 (lldb.process), type = 
> 0x0001(state-changed), data = { process = 004BC308 (pid = 1), state = 
> stopped}}, unique =0) hijack = 
> 1442428969.47300 00402598 Listener('lldb.Debugger')::AddEvent (event_sp = 
> {00A723C8})
> 1442428969.47400 004BC42C Listener::WaitForEventsInternal (timeout = { 
>  }) for lldb.process.internal_state_listener
>
> Here's the code I use to attach.
>
> SBDebugger::Initialize();
>
> SBDebugger debugger = lldb::SBDebugger::Create(false);
> debugger.SetAsync(true);
>
> const char* categories [] = { "process", "events", 0 };
> if (!debugger.EnableLog("lldb", categories))
> return -1;
>
> pid_t pid = 1;
>
> SBTarget target = debugger.CreateTargetWithFileAndArch(elffile_name, "opus2");
>
> SBError error;
> SBListener listener("test_listener");
>
> SBProcess process = target.AttachToProcessWithID(listener, pid, error);
>
> if (!process.IsValid())
> {
>...
>
>
> I would be grateful for any insight on the cause of this behavior.
>
> Thanks,
> -Philippe
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev