[news.eclipse.platform.swt] Re: X error caused by DND

[duongn@xxxxxxxxxx (Duong Nguyen)]

Yes. This looks like a bug so please enter one in bugzilla. If there's a 
stack trace in the log, can you include it in the bug report. 

Thanks,
Duong

Emil Crumhorn wrote:

> If you don't find the bug in bugzilla, then it sounds like a new bug.

> Please take a look here first however if there's either a similar bug or 
> there existing a workaround for your problem:

> https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=BadWindow

> Regards,
> Emil


> "David Huebel" <davidhuebel@xxxxxxxxxxx> wrote in message 
> news:fvak52$jkq$1@xxxxxxxxxxxxxxxxxxxx
> > I very occasionally get errors like the one below when dragging data in my
> > RCP application under Linux.  I'm not sure exactly what triggers the 
> > error.
> > DND works most of the time under Linux, and I've never seen an error under
> > Windows.
> >
> > Is it possible that the bug is in my application code, or should I write 
> > it
> > off as a platform bug?
> >
> > -David
> >
> > The program '******* ********' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadWindow (invalid Window parameter)'.
> >  (Details: serial 108665 error_code 3 request_code 3 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 --sync command line
> >   option to change this behavior. You can then get a meaningful
> >   backtrace from your debugger if you break on the gdk_x_error() 
> > function.)