How to start on debugging this Swing/AWT error?

arnet_at_hpcvplnx.cv.hp.com
Date: 10/15/03 

Date: Wed, 15 Oct 2003 16:54:35 GMT

I'm wondering about what techniques to use to debug an
error which is coming from somewhere in the guts of a
large piece of code I didn't write, with no indication
of where. I'm using JDK1.3.

The problem is that the error stack trace does not list
any part of the actual user code in the trace, which
puzzles me. Without this, I don't even know which of the
several dozen classes that may be generating it to
look at.

I've appended the error below. I don't need to know what
it mean, I basically know that. I need to know how I
could approach finding where in the code it is coming from.
In other cases I've worked in the stack trace always gave
be at least some clue.

Thanks,

--arne

DISCLAIMER: These opinions and statements are those of the author and
do not represent any views or positions of the Hewlett-Packard Co.

Exception occurred during event dispatching:
java.lang.ArrayIndexOutOfBoundsException: No such child: 3
        at java.awt.Container.getComponent(Container.java:170)
        at javax.swing.JComponent.rectangleIsObscured(JComponent.java:3615)
        at javax.swing.JComponent.paint(JComponent.java:737)
        at javax.swing.JLayeredPane.paint(JLayeredPane.java:546)
        at javax.swing.JComponent.paintWithBuffer(JComponent.java:4393)
        at javax.swing.JComponent._paintImmediately(JComponent.java:4336)
        at javax.swing.JComponent.paintImmediately(JComponent.java:4187)
        at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:370)
        at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:205)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:317)
        at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:103)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:84)

Relevant Pages

  • Re: Debug vs. Release code.
    ... In regards to being able to log a stack trace. ... I have noticed that if I do not have the PDB files on the target ... So far having a Debug build seems to be the only way that I know ...
    (microsoft.public.dotnet.framework.clr)
  • Re: Downside of using Debug builds for production
    ... use of Microsoft's Exception Handling application block. ... the process if I desire to debug the application. ... For example, an "optimized" build could in some cases be larger than the "non-optimized" build, depending on what the optimization goals are. ... it seems to me that you are really only interested in one aspect of the "debug" build: the inclusion of symbols allowing for the stack trace to include line numbers in the exceptions. ...
    (microsoft.public.dotnet.framework)
  • trouble with PrepareToEncode and vct3216.dll
    ... The stack trace ... lists vct3216 as the problem. ... I have seen posts as far back as fives years ... but I am seeing the same problem on debug or release. ...
    (microsoft.public.windowsmedia.sdk)
  • Re: ASSERT on a line not where program breaks
    ... Your assertion is coming from ATL code, and most likely has to do with your HWND or the ... "Retry" button to debug the application, I don't break in to line 460, ... stack trace below for reference. ...
    (microsoft.public.vc.language)
Loading