Re: Debug gb.desktop

[gbWilly <gbWilly@xxxxxxxxxxxxxx>]

On Saturday, July 4th, 2026 at 10:59, Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 30/06/2026 à 14:08, gbWilly a écrit :
> > On gambas.one someone encountered some occasional trouble using gb.desktop
> >
> > This is the message he gets in IDE:
> > 'BadWindow (invalid Window parameter)'.
> >    (Details: serial 63739 error_code 3 request_code 20 (core protocol)
> > minor_code 0)
> >    (Note to programmers: normally, X errors are reported asynchronously;
> >     that is, you will receive the error a while after causing it.
> >     To debug your program, run it with the GDK_SYNCHRONIZE environment
> >     variable to change this behavior. You can then get a meaningful
> >     backtrace from your debugger if you break on the gdk_x_error()
> > function.)
> >
> > His question is how he can debug gb.desktop from IDE, so some more
> > details on what goes wrong are provided.
> >
> > Anyone know how?
> >
> > gbWilly
> >
> > GambOS <https://gambos.gambas.one/>
> > Gambas3 for Debian/Ubuntu <https://gitlab.com/gbWilly/gambas3-debian-
> > repository>
> > <https://gambos.gambas.one/>
> >
> > *...there is always a Catch if things go wrong!*
> >
> > Sent with Proton Mail <https://proton.me/mail/home> secure email.
> 
> He must do what is written in the error message: set GDK_SYNCHRONIZE to
> "1". Then the program will crash exactly at the bad X11 function call.
> 

Here is what I got back.

In the Project -> Properties -> Tab environment he added GDK_SYNCHRONIZE with value 1.
Next he run the project from IDE and got a likewise error telling him again what above error message already stated.

BadWindow (invalid Window parameter)'.
  (Details: serial 21138 error_code 3 request_code 20 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.) 

Seems like the set environment is not taken into account when set in the project.
Is he doing something wrong?

gbWilly

GambOS
Gambas3 for Debian/Ubuntu

...there is always a Catch if things go wrong!

Sent with Proton Mail secure email.