[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-2d-dev
Subject:    [OpenJDK 2D-Dev] Where/Why are X11 errors caught?
From:       Dmitri.Trembovetski () Sun ! COM (Dmitri Trembovetski)
Date:       2008-08-14 19:51:42
Message-ID: 48A48CCE.6060600 () Sun ! COM
[Download RAW message or body]



   I believe AWT installs their own error handler which traps
   the errors. It should be somewhere in awt_GraphicsEnv.c or
   around there. Look for where they open the display.

   You can install your own handler to override theirs -
   check out how it's done when we detect if shared memory
   extension is available.

   Also, I think there's a compile time flag that you can use
   which enables debug output of X11 errors.

   Thanks,
     Dmitri


Clemens Eisserer wrote:
> Hello,
> 
> When working on the XRender pipeline I always wondered why X11 errors
> did not abort java.
> Eg. for small test programs written in C the application aborts when a
> "BadMatch" error occurs, with the X11 pipeline I don't even see the
> error - it just does not work.
> 
> Is there any way to get the errors reported somehow?
> Currently my pipeline does not work on solaris as intended and maybe
> this way I would be able to find the cause.
> 
> Thanks in advance, Clemens


[prev in list] [next in list] [prev in thread] [next in thread]