package codePoint;

public class StringFromCodePoint {
	public static void main(String[] args) {
		
		// Russian letters.
		System.out.print("Russian letters: ");
		for (int i = 1040; i<=1103; i++)
			System.out.print(newString(i));
		
		System.out.println();
		
		// Chinese symbol.
		System.out.println("Chinese symbol: " + newString(37329));
		
		char c = 37329;
		System.out.println(c);
		
		// char c2 = 65536; Compile error char type is limited by 65535. 
		System.out.println("symbol: " + newString(2000000));
	}
	
	static String newString(int codePoint) {
	    if (Character.charCount(codePoint) == 1) {
	        return String.valueOf((char) codePoint);
	    } else {
	        return new String(Character.toChars(codePoint));
	    }
	}
	
}

// http://www.oracle.com/us/technologies/java/supplementary-142654.ht

System.out.println("symbol: " + newString(2000000));

return new String(Character.toChars(codePoint));

    public static char[] toChars(int codePoint) {
        if (isBmpCodePoint(codePoint)) {
            return new char[] { (char) codePoint };
        } else if (isValidCodePoint(codePoint)) {
            char[] result = new char[2];
            toSurrogates(codePoint, result, 0);
            return result;
        } else {
            throw new IllegalArgumentException();
        }
    }

Update the build path of the project to use a JDK instead of JRE.
JREs do not include debug information
(https://stackoverflow.com/questions/22205155/debug-point-inside-the-java-util-class).

Step filters are commonly used to filter out types that you do not wish to see or step through while debugging.

For example, if you did not want to the see or step through anything from the class java.lang.Object, you would add this to the list of filtered types.