On Mon, Aug 24, 2015 at 05:37:43PM -0700, via lldb-dev wrote:
> On Mon, Aug 24, 2015 at 03:37:52PM -0700, Todd Fiala via lldb-dev wrote:
> > On Linux on non-virtualized hardware, I currently see the failures below on
> > Ubuntu 14.04.2 using a setup like this:
> > [...]
> >
> > ninja check-lldb ou
https://llvm.org/bugs/show_bug.cgi?id=24869
Bug ID: 24869
Summary: dotest.py reports the wrong number of test cases in
mutiprocess mode.
Product: lldb
Version: unspecified
Hardware: PC
OS: All
St
Yes, it is working now. I can set breakpoints, step, wait for events, etc.
Thanks for your help!
-Philippe
From: Greg Clayton [gclay...@apple.com]
Sent: Thursday, September 17, 2015 3:42 PM
To: Philippe Lavoie
Cc: Jim Ingham; lldb-dev@lists.llvm.org
Subjec
Yep, that'll do it!
Are you up and running now?
> On Sep 17, 2015, at 11:05 AM, Philippe Lavoie
> wrote:
>
>
> Ah! The issue was in my custom Platform's Attach. It is based on PlatformGDB,
> but it seems I bulldozed through a little too fast.
>
> I was missing a call to Process::HijackProce
Ah! The issue was in my custom Platform's Attach. It is based on PlatformGDB,
but it seems I bulldozed through a little too fast.
I was missing a call to Process::HijackProcessEvents before calling
Process::Attach
auto listener =
attach_info.Get
On Thu, Sep 17, 2015 at 10:39 AM wrote:
> On Thu, Sep 17, 2015 at 05:20:14PM +, Zachary Turner wrote:
> > > > a) they should be explicitly marked as interface tests.
> > > What's the decorator for this?
> >
> > There's not one currently.
>
> Will there be?
>
Whenever someone adds one :) If y
On Thu, Sep 17, 2015 at 05:20:14PM +, Zachary Turner wrote:
> > > a) they should be explicitly marked as interface tests.
> > What's the decorator for this?
>
> There's not one currently.
Will there be?
> > > d) Results of these interface tests should also not be *verified* by the
> > > use
On Thu, Sep 17, 2015 at 10:31 AM wrote:
> On Tue, Sep 15, 2015 at 04:46:41PM -0700, Jim Ingham wrote:
> > > In any case, there's a lot I never could figure out how to do in the SB
> > > API that I could only do via commands. For example, how do you test
> > > that a trailing space at the end of
On Tue, Sep 15, 2015 at 04:46:41PM -0700, Jim Ingham wrote:
> > In any case, there's a lot I never could figure out how to do in the SB
> > API that I could only do via commands. For example, how do you test
> > that a trailing space at the end of the expr --language option's argument
> > is trimm
> On Sep 17, 2015, at 10:14 AM, Ryan Brown wrote:
>
>
>
> On Thu, Sep 17, 2015 at 10:06 AM Greg Clayton via lldb-dev
> wrote:
>
> > On Sep 17, 2015, at 3:08 AM, Bruce Mitchener
> > wrote:
> >
> > Howdy!
> >
> > I was looking at some of the CompilerType changes and had some questions
> >
On Thu, Sep 17, 2015 at 10:08 AM wrote:
> On Tue, Sep 15, 2015 at 11:36:00PM +, Zachary Turner wrote:
> > a) they should be explicitly marked as interface tests.
>
> What's the decorator for this?
>
There's not one currently.
>
> > d) Results of these interface tests should also not be *ver
On Thu, Sep 17, 2015 at 10:06 AM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> > On Sep 17, 2015, at 3:08 AM, Bruce Mitchener
> wrote:
> >
> > Howdy!
> >
> > I was looking at some of the CompilerType changes and had some questions
> related to the recent cleanups and renamings.
This sounds like you don't have a private state thread running. The private
state thread watches for private state changes in Process and promotes them
into public state changes as needed. Can you check if
Process::PrivateStateThread() is running? This should be triggered by a call to
StartPriv
> On Sep 17, 2015, at 3:08 AM, Bruce Mitchener
> wrote:
>
> Howdy!
>
> I was looking at some of the CompilerType changes and had some questions
> related to the recent cleanups and renamings.
>
> • clang_type_t is a typedef for void* and is used for the opaque qual
> type code among o
On Tue, Sep 15, 2015 at 11:36:00PM +, Zachary Turner wrote:
> a) they should be explicitly marked as interface tests.
What's the decorator for this?
> d) Results of these interface tests should also not be *verified* by the
> use of self.expect, but itself through the API. (Relying on the te
I am missing the final SetPublicState call.
1442509021.49000 Process::SetPrivateState (connected)
1442509021.49200 Process::SetPublicState (state = attaching, restarted = 0)
1442509021.62700 Process::SetPrivateState (stopped)
1442509021.62800 Process::SetPrivateState (stopped) stop
Here is the output of attaching to a process with ProcessGDBRemote:
(lldb) log enable lldb state
(lldb) attach 12406
Process::SetPublicState (state = attaching, restarted = 0)
Process::SetPrivateState (stopped)
Process::SetPrivateState (stopped) stop_id = 1
Process::SetPublicState (state = stopped
Howdy!
I was looking at some of the CompilerType changes and had some questions
related to the recent cleanups and renamings.
- clang_type_t is a typedef for void* and is used for the opaque qual
type code among other things. However, the m_type on CompilerType is just a
void*. Should
18 matches
Mail list logo
