Bug 1767 - Display ASCII for values greater than 127 fails (1GLE8I5)
Summary: Display ASCII for values greater than 127 fails (1GLE8I5)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: All Linux
: P1 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Mike Wilson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:18 EDT by Jared Burns CLA
Modified: 2001-12-07 10:48 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2001-10-10 22:18:58 EDT
public class Hello() {

	public static void main(String[] args) {
		int x= 255
		int y= 67;
		System.out.println("Hello, World!");
	}

}

1. Turn on the "Display ASCII values" preference.
2. Place a breakpoint on line 6 ("System.out") and debug Hello
3. Note that x's label is completely empty in the variables view

I've debugged this enough to see that the JDIModelPresentation *is*
generating and returning the correct label for x.

NOTES:
Comment 1 Darin Wright CLA 2001-10-15 11:51:36 EDT
If we are generating the correct label, why is it not displaying?
Comment 2 Jared Burns CLA 2001-10-15 18:10:36 EDT
This bug is actually much worse than I thought. It's not at all related to the
ASCII display preference.
We completely bomb when trying to display any string that contains a char > 127.
This bug is new to the 2.0 stream.

public class Hello() {
	public static void main(String[] args) {
		char c= (char) 255;
		System.out.println("Hello, world!"); // breakpoint here
	}
}
Comment 3 Jared Burns CLA 2001-10-17 15:02:37 EDT
Appears to be a Linux-only SWT or UI bug.
Comment 4 DJ Houghton CLA 2001-10-24 06:40:21 EDT
PRODUCT VERSION:
2.0 stream

Comment 5 Grant Gayed CLA 2001-10-24 11:44:08 EDT
Fixed by Silenio.  We now use memmove to ensure that the bytes are moved in the 
correct order according to the endianness of the platform.

This introduces a limitation on RedHat 6.2, which is fine since this is not a 
2.0-supported platform.  This has been documented in the swt readme (99.1.11 
Non ASCII strings on Linux).