Sign in Join

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

Mailing lists / lazarus / 2010-11

IDE: Gdk-CRITICAL error

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

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

patspiper

I get sometimes the following error when I click on any IDE window: (lazarus:4991): Gdk-CRITICAL **: gdk_window_get_state: assertion `GDK_IS_WINDOW (window)' failed

What is 4991, and what does this error mean?

Reply by email

Marc Weustink
to patspiper
patspiper wrote 5 lines
I get sometimes the following error when I click on any IDE window: (lazarus:4991): Gdk-CRITICAL **: gdk_window_get_state: assertion `GDK_IS_WINDOW (window)' failed What is 4991, and what does this error mean?

4991 is I guess your process id.
The error means that we call a function which expects a gdk_window pointer, but we pass something else, probably a nil. It doesn't hurt, since gdk/gtk checkes against nil. It only prints these messages and means that we need to find the call and check for nil.

Marc

Reply by email

Henry Vermaak
to Marc Weustink
Marc Weustink wrote 12 lines
patspiper wrote: > I get sometimes the following error when I click on any IDE window: > (lazarus:4991): Gdk-CRITICAL **: gdk_window_get_state: assertion > `GDK_IS_WINDOW (window)' failed > > What is 4991, and what does this error mean? 4991 is I guess your process id. The error means that we call a function which expects a gdk_window pointer, but we pass something else, probably a nil. It doesn't hurt, since gdk/gtk checkes against nil. It only prints these messages and means that we need to find the call and check for nil.

You may be able to find out where this is happening by running gdb --args ./lazarus --g-fatal-warnings. GTK will then sigabrt on a warning and you can get a backtrace.

Henry

Reply by email

patspiper
to Marc Weustink: 4991 is I guess your process id. The error means that we call a function which expects a…
Marc Weustink wrote 6 lines
The error means that we call a function which expects a gdk_window pointer, but we pass something else, probably a nil. It doesn't hurt, since gdk/gtk checkes against nil. It only prints these messages and means that we need to find the call and check for nil. Marc

This could then mean as well a call with wrong arguments, especially that it rarely occurs.

Reply by email