This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I set to JPDA fo Default Debugging and set a breakpoint in class file of japanese, debugging can not stop at the breakpoint and just exits. I've verified this problem happens on NT and Win2K. When I switch to JDK 1.1 debugger implement, this problem does not happen. Also if class name is ascii, there is no problem. The example is very simple, which has only main() method, public class <japanese> { public <japanese> { } public static main (String args[]) { String var="test"; System.out.println(var); // set breakpoint here } }
Can you attach a class file created by compiling a source containing a class named in Japanese to reproduce the problem, please ?
Created attachment 2912 [details] test.zip file contains the examples of Windows platform
Related JDK bugs: http://developer.java.sun.com/developer/bugParade/bugs/4473954.html http://developer.java.sun.com/developer/bugParade/bugs/4475696.html http://developer.java.sun.com/developer/bugParade/bugs/4185525.html http://developer.java.sun.com/developer/bugParade/bugs/4187490.html
This bug is causes by JDK bug. Not only you cannot debug class with Japanese classname but you cannot even start such a class from command-line. java <japanese-name> ... fails (Class not found.) But you _can_ debug classes with Japanese name if the application's main class contains only english characters. So there is a simple workaround: Create an english-named class that just calls the Japanese class's method 'main(...)': file EnglishClass.java: public class EnglishClass { public static void main(String args[]) { <JapaneseClass>.main(args); } } file <JapaneseClass>.java: public class <JapaneseClass> { public static void main(String args[]) { ... } } To run (or debug) <JapaneseClass>, type: java EnglishClass
This FFJ bug is most probably caused by JDK bug #4498715 ("filename with japanese characters"). It does not manifest if you use Japanese Solaris 8 with Unicode encoding (select language "ja_JP.UTF-8" in the login dialog). Maybe some workaround for the JDK bug could be added into Forte but because a simple workaround exists we will not do it.
Wontfix -> Closed.