Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / qt / 2007-08

QApplication::notify: Unexpected null receiver

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Павел Ишенин

Hello, Items specific to the Qt widget set

Sorry, I have not searched deeply, but it is seems to me that this message is generated b bindings. After that message my qt applications usually crash. I just want to know:
- reason of message
- how to prevent
- if it is not possible to prevent then how to workaround crash

Best regards,
Paul Ishenin.

Reply by email

Unknown author
to Павел Ишенин

Quoting ????? ?????? :

Show quoted text 8 lines
Hello, Items specific to the Qt widget set Sorry, I have not searched deeply, but it is seems to me that this message is generated b bindings. After that message my qt applications usually crash. I just want to know: - reason of message - how to prevent - if it is not possible to prevent then how to workaround crash

1.can you provide any test case about this / which control crashes app ? 2.any gdb backtrace ?

I havent seen this message till early days of qt bindings (under linux). eg. we had bug when you click with right mouse button on to ttreeview it crashes app and there's your message, or eg. we just called QWidget_destroy(OurWidgetHandle) and boooom (really early days of bindings) some QEvent still processing,but handle is dead, or eg. WideString problem we had about 1-2 months ago.
If I can reproduce this message, I'll find all answers to your question.

zeljko

Reply by email

Павел Ишенин
to Unknown author
Show quoted text 11 lines
1.can you provide any test case about this / which control crashes app ? 2.any gdb backtrace ? I havent seen this message till early days of qt bindings (under linux). eg. we had bug when you click with right mouse button on to ttreeview it crashes app and there's your message, or eg. we just called QWidget_destroy(OurWidgetHandle) and boooom (really early days of bindings) some QEvent still processing,but handle is dead, or eg. WideString problem we had about 1-2 months ago. If I can reproduce this message, I'll find all answers to your question.

I cant. It happens not ofter while playing with qt ide. Try to open/close some dialogs and maybe you'll be lucky.

Best regards,
Paul Ishenin.

Reply by email

zeljko
to Павел Ишенин
????? ?????? wrote 13 lines
> 1.can you provide any test case about this / which control crashes app ? > 2.any gdb backtrace ? > > I havent seen this message till early days of qt bindings (under linux). > eg. we had bug when you click with right mouse button on to ttreeview > it crashes app and there's your message, or eg. we just called > QWidget_destroy(OurWidgetHandle) and boooom (really early days of > bindings) some QEvent still processing,but handle is dead, or eg. > WideString problem we had about 1-2 months ago. > If I can reproduce this message, I'll find all answers to your question. I cant. It happens not ofter while playing with qt ide. Try to open/close some dialogs and maybe you'll be lucky.

aha...so you get it in IDE. I've seen some things this morning, and thoses are async replys from X server on linux in ide console , I'll try to provoke IDE to make it ...

Reply by email

zeljko
to Павел Ишенин: I cant. It happens not ofter while playing with qt ide. Try to open/close some dialogs…
????? ?????? wrote 14 lines
> 1.can you provide any test case about this / which control crashes app ? > 2.any gdb backtrace ? > > I havent seen this message till early days of qt bindings (under linux). > eg. we had bug when you click with right mouse button on to ttreeview > it crashes app and there's your message, or eg. we just called > QWidget_destroy(OurWidgetHandle) and boooom (really early days of > bindings) some QEvent still processing,but handle is dead, or eg. > WideString problem we had about 1-2 months ago. > If I can reproduce this message, I'll find all answers to your question. I cant. It happens not ofter while playing with qt ide. Try to open/close some dialogs and maybe you'll be lucky.

hm.. I've found a bunch of next messages:

QPainter::begin: Cannot paint on a null pixmap
----
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 40 (X_TranslateCoords)
Resource id: 0x3202a71
....

Also when I copy something from SynEdit, and try to paste it into kwrite it freezes kwrite completelly ....

Reply by email