Discussion:
[Interest] Good way to track down "QCoreApplication::postEvent: Unexpected null receiver"
Bob Hood
2015-12-06 18:44:02 UTC
Permalink
I'm getting this warning/error, but it's pretty nebulous in terms of where
exactly it is occurring. Is there some kind of debug switch I can enable to
get move verbose output when this occurs, perhaps something that would help me
pinpoint the culprit?
Samuel Gaist
2015-12-06 20:46:59 UTC
Permalink
Hi,

That usually occurs when you are calling deleteLater on a null QObject.

First thing I'd check are delete and deleteLater statements of QObject derived class.

Cheers

Samuel
I'm getting this warning/error, but it's pretty nebulous in terms of where exactly it is occurring. Is there some kind of debug switch I can enable to get move verbose output when this occurs, perhaps something that would help me pinpoint the culprit?
_______________________________________________
Interest mailing list
http://lists.qt-project.org/mailman/listinfo/interest
Bob Hood
2015-12-07 02:03:38 UTC
Permalink
Post by Samuel Gaist
Hi,
That usually occurs when you are calling deleteLater on a null QObject.
First thing I'd check are delete and deleteLater statements of QObject derived class.
Ah, excellent. That at least lets me know where to focus my attention.

Thank you, Samuel.
Giuseppe D'Angelo
2015-12-06 22:49:25 UTC
Permalink
Post by Bob Hood
I'm getting this warning/error, but it's pretty nebulous in terms of where
exactly it is occurring. Is there some kind of debug switch I can enable to
get move verbose output when this occurs, perhaps something that would help
me pinpoint the culprit?
Run with QT_FATAL_WARNINGS=1? Add a breakpoint on the qWarning
statement in question inside Qt?
--
Giuseppe D'Angelo
Bob Hood
2015-12-07 02:04:21 UTC
Permalink
Post by Giuseppe D'Angelo
Post by Bob Hood
I'm getting this warning/error, but it's pretty nebulous in terms of where
exactly it is occurring. Is there some kind of debug switch I can enable to
get move verbose output when this occurs, perhaps something that would help
me pinpoint the culprit?
Run with QT_FATAL_WARNINGS=1? Add a breakpoint on the qWarning
statement in question inside Qt?
Good point, Giuseppe. I did not know about that variable. I'll try that and
see if it helps.

Thanks so much.

Loading...