7000913: (bf) CharBuffer.wrap, slice, position, slice leads to CharBuffer with incorrect offset

Alan Bateman Alan.Bateman at oracle.com
Thu Nov 18 02:35:09 PST 2010

This one came up on core-libs-dev yesterday [1]. If a CharBuffer is 
created by wrapping a CharSequence, the resulting buffer is sliced, and 
the slice further sliced when the position is non-zero, then the 
resulting CharBuffer doesn't have the correct offset. I'm not sure if 
John found this by inspection or ran into the issue. Here's the webrev 
with the changes, it's mostly an update to an existing test as this case 
seems to have been missed:



More information about the nio-dev mailing list