Re: Ugly ugly Gdk error




Havoc Pennington <rhp@zirx.pair.com> writes:

> On Mon, 31 May 1999, Fiachra wrote:
> > I was hoping someone could give me some insight on what I should look for when
> > fixing this error:
> > 
> > Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter)
> >   serial 132 error_code 9 request_code 14 minor_code 0
> > 
> > aborting...
> > Aborted (core dumped)  
> > 
> > At least I would like to know what GDK is trying to do when an error like this
> > shows up.
> > 
> 
> Run your application in gdb, and type backtrace after the error to see
> which Gdk function the error occurred in. Many different functions can
> cause this - as it says, it just means you tried to use a pixmap or window
> that wasn't valid, perhaps because it was destroyed or something.

Because this error is a X error, it may be reported asynchronously.
To get a good backtrace, you should run your program as:

 (gdb) r --sync

Otherwise, the error may be reported some time after the code
that triggered the error is run.

Regards,
                                        Owen




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]