trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2013

Re: [trinity-devel] commit 99b03be6 (qt3/tqt3)

From: Slávek Banko <slavek.banko@...>
Date: Mon, 4 Nov 2013 22:09:36 +0100
On Monday 04 of November 2013 21:32:06 Timothy Pearson wrote:
> > Hi all,
> >
> > after commit 99b03be6 I have on a test machine in .xsession-errors many
> > such reports. Note that it is the testing machine, on which is now the
> > only active screen saver.
> >
> > TQThreadInstance::finish: In TQThreadInstance::finish for thread
> > 0x1508ad0
> >
> > TQThreadInstance::finish: In TQThreadInstance::finish for thread
> > 0x150b400
> >
> > TQThreadInstance::finish: In TQThreadInstance::finish for thread
> > 0x150afb0
> >
> > TQThreadInstance::finish: In TQThreadInstance::finish for thread
> > 0x1508af0
> >
> > TQThreadInstance::finish: In TQThreadInstance::finish for thread
> > 0x150b420
>
> That was supposed to be wrapped in a QT_DEBUG #ifdef.  I'll fix that ASAP.
>
> > To this I have two questions:
> >
> > 1) How can such a report be useful when there is no knowing what
> > applications are affected?
> >
> > 2) Tim, why you use in such reports, a new lines with "\r"?
>
> Old habits.  I'll fix that as well. ;-)
>

That explains it. I just wondered if I was not overlooked something 
important :)

> Tim
>

Slavek
--