Edward Welbourne wrote:
Interesting way such as LTTNG/ETW :) ?
>
>>> Spoiler alert: not on Mac ...
>
> Konstantin Tokarev (31 August 2017 15:50)
>> Mac has DTrace
>
> Do we have anyone eager to follow up on the LLTNG/ETW work
> (see earlier mail in this thread for link), adding DTrace for
On Thursday, 31 August 2017 01:35:08 PDT René J. V. Bertin wrote:
> > Source compatibility. Which is why it's unlikely we'll do it.
>
> Qt6 isn't going to break anything that builds against a sufficiently recent
> Qt5 version?
See the other email where I said that this changing this is likely to
>>> Interesting way such as LTTNG/ETW :) ?
>> Spoiler alert: not on Mac ...
Konstantin Tokarev (31 August 2017 15:50)
> Mac has DTrace
Do we have anyone eager to follow up on the LLTNG/ETW work
(see earlier mail in this thread for link), adding DTrace for Mac ?
Eddy.
__
31.08.2017, 16:48, "René J. V. Bertin" :
> Sergio Martins wrote:
>
>> Interesting way such as LTTNG/ETW :) ?
>
> Spoiler alert: not on Mac ...
Mac has DTrace
>
> R.
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-pro
Sergio Martins wrote:
> Interesting way such as LTTNG/ETW :) ?
Spoiler alert: not on Mac ...
R.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Thiago Macieira wrote:
>> Source compatibility. Which is why it's unlikely we'll do it.
René J. V. Bertin 31 August 2017 10:35
> Qt6 isn't going to break anything that builds against a sufficiently
> recent Qt5 version?
I doubt that; but the fact that we may break SC at Qt6 doesn't
necessarily me
On 2017-08-30 23:13, Thiago Macieira wrote:
Ok, so you found by git bisect (or similar) action. I was hoping you
had some
interesting way of debugging that the problem is timers constantly
firing. I
woder if GammaRay can give you a list of timers active in a thread and
which
objects it's conne
On 31 Aug 2017, at 08:57, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Wednesday, 30 August 2017 23:12:40 PDT Lars Knoll wrote:
a) revert the 5.6 backport of 88a8feeacb9bdaff9ee06164424e407eb904cd10 so
that 5.6.x will forever calculate Keccak, not SHA3;
b) additionally backport
Hi,
Re: change which caused the CPU burning issue I discovered a couple of days
back ("[fix]: Assistant (and others) burning CPU because of
#f27d1ccbb24ec2fd4098f2976503478831006cc8 ?"). It intrigued me why an
application that doesn't use native Mac menus would be calling [NSMenu update]
at al
Thiago Macieira wrote:
>> I guess so :) I still don't get what purpose calling QObject::timerEvent()
>> has if the method itself does nothing. Gives me something to ponder.
>
> Again, that's what makes QTimer possible.
>
> void QTimer::timerEvent(QTimerEvent *e)
> {
> if (e->timerId() == id)
On Thursday, 31 August 2017 00:13:43 CEST Thiago Macieira wrote:
> On Wednesday, 30 August 2017 14:17:05 PDT René J. V. Bertin wrote:
> > Thiago Macieira wrote:
> >
> > Oops, missed this one.
> >
> > > Unfortunately, we can't change anymore.
> >
> > Can someone explain what could possibly be bro
11 matches
Mail list logo
