Created attachment 73148 [details]
No Stop at this breakpoint

I can not reproduce this. Execution stops on the breakpoint for me.
Do other breakpoints in the same source file work? Does really execution go through this point in your case? Did you
wait for some time? After the breakpoint was hit for the first time, when I did continue, the test was running for some
time and after that the breakpoint was hit again.

I've tried to reproduce it with RC2. You are right, debugger stops here.

But I've found another breakpoint, which doesn't stop. See attachment.
(Checkout rev=495)

This issue seems to be a little mysterious. Since a couple of days, I experience, that that locations, where breakpoints
don't stop, vary from day to day. So randomly try out different locations.
Today, it stops, if breakpoint is in line 29 of AsciiPagedMapEncoder, but not in line 33.

Created attachment 73711 [details]
Another not stopping breakpoint

Attention: Maybe I'm wrong with last example.
... but now I must go to bed. Let me try tomorrow again.

Hi,

I have checked out this revision (476) in new empty folder, and I can always reproduce this issue with RC1. Maybe
following is important:
- Run on Windows machine.
- Default charset on this machine must be "windows-1252" (I use German version of Windows XP prof. here).
I assume, that the code, where I set the breakpoint, is executed in initialization phase of the additional JVM (here JDK
1.6.0u3), and that in this state, debugger api is disabled, so Netbeans IDE can't catch the breakpoint.
Note, that my classes are preloaded by
-Xbootclasspath/p:${build.classes.dir}${path.separator}${run.test.jvmargs.xbootclasspath}

You can also set breakpoints in class sun.nio.cs.MS1252 (see next attachment). NetBeans debugger will only stop in
method newDecoder(), but not in constructor and not in initializing static variable.


I will also check this with RC2.

Created attachment 73801 [details]
Breakpoints in class sun.nio.cs.MS1252

Now I also have checked with RC2. I can reproduce same behaviour here. :-)

I can also reproduced the issue with current head revision of my project.

Reproduced.
Debugger really doesn't stop on the constructor, line 17. However, it stops on line 50 in the body of the class method.  

Product Version: NetBeans IDE 6.5 (Build 200811100001)
Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15
System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb)

Thanks for detailed description, I've reproduced this also on Linux with default charset UTF-8. Breakpoints in
MS1252.java work fine, but breakpoints in UTF_8.java behave as you describe - no hits in constructor or static
initialization, but in other methods all hits are fine.

IMHO this is not fixable, it's just how it (JVM) works.

I'm going to try this outside of NetBeans, using jdb...

This definitely can not be fixed in NetBeans. If you think that this is a bug, submit a defect for JVM at
http://bugs.sun.com/

I've started the test in debug mode on console. While it waited for the debugger to connect, I've started jdb, attached
to it and listed the loaded classes. Besides many other, following classes from your project were already loaded:
sun.nio.cs.FastCharsetProvider
sun.nio.cs.HistoricallyNamedCharset
sun.nio.cs.StandardCharsets
sun.nio.cs.StandardCharsets$Aliases
sun.nio.cs.StandardCharsets$Cache
sun.nio.cs.StandardCharsets$Classes
sun.nio.cs.StreamDecoder
sun.nio.cs.StreamEncoder
sun.nio.cs.Surrogate$Generator
sun.nio.cs.Surrogate$Parser
sun.nio.cs.UTF_8
sun.nio.cs.UTF_8$Decoder
sun.nio.cs.UTF_8$Encoder
sun.nio.cs.Unicode

I've submitted the breakpoints and only the breakpoint in method was hit, exactly like when run in Netbeans:
Breakpoint hit: "thread=main", sun.nio.cs.UTF_8$Decoder.decodeArrayLoop(), line=69 bci=0

Thanks for evaluating this from console. I'm not experienced in using console.

Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.