Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Fix SeekEnd direction and ReadInt24 sign extension by youdie006 · Pull Request #131 · tdewolff/parse · GitHub
Skip to content

Fix SeekEnd direction and ReadInt24 sign extension - #131

Open
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24
Open

Fix SeekEnd direction and ReadInt24 sign extension#131
youdie006 wants to merge 1 commit into
tdewolff:masterfrom
youdie006:binaryreader-seekend-int24

Conversation

@youdie006

Copy link
Copy Markdown

Two bugs in BinaryReader, both in the part of binary.go that no test or in-tree caller reaches.

1. Seek with io.SeekEnd moves the wrong way

binary.go:316 says // Seek complies with io.Seeker. For whence == 2 the guard is already
right — off must be in [-Len(), 0] — but the arithmetic subtracts it (binary.go:332):

r.pos=r.f.Len() -off

With a negative offset that lands past the end. Against bytes.Reader, the standard library's
io.Seeker, on an 8-byte buffer:

Seek( 0, SeekEnd) stdlib=8 parse=8
Seek( -1, SeekEnd) stdlib=7 parse=9 mismatch
Seek( -4, SeekEnd) stdlib=4 parse=12 mismatch
Seek( -8, SeekEnd) stdlib=0 parse=16 mismatch

and no error is returned, so reading the last four bytes silently yields zeros:

Seek(-4, io.SeekEnd) -> pos=12, err=<nil>
ReadUint32() -> 0x00000000 (want 0x05060708)

2. ReadInt24 does not sign-extend

binary.go:441:

func (r*BinaryReader) ReadInt24() int32 {
returnint32(r.ReadUint24())
}

ReadInt8/16/32/64 get the sign for free because the conversion keeps the width. There is no
int24, so the 24-bit value is zero-extended into an int32 and every negative number comes back
positive. The package's own writer is the oracle:

WriteInt24( -1) -> ff ff ff -> ReadInt24() = 16777215
WriteInt24( -2) -> ff ff fe -> ReadInt24() = 16777214
WriteInt24(-8388608) -> 80 00 00 -> ReadInt24() = 8388608
for contrast: Int8 -1 -> -1, Int16 -1 -> -1, Int32 -1 -> -1

Change

binary.go:332: - becomes +. binary.go:441: sign-extend from bit 23,
int32(r.ReadUint24()<<8) >> 8.

Why these survived

grep -c "Seek\|ReadInt24" *_test.go is 0 in every test file, and binary.go has no in-tree
caller outside its own definitions — so neither line has ever been executed by the suite.

Tests added to binary_test.go in the existing style: the four SeekEnd offsets checked against
their expected positions plus the read that follows, and a WriteInt24/ReadInt24 round trip over
-1, -2, -8388608, 0, 1, 8388607. Red with only binary.go reverted, green with the
change; go test -race -count=1 ./... passes across all packages and gofmt -l is clean on both
files.

Happy to split these into two PRs if you would rather review them separately — they are independent
apart from living in the same untested file.


Disclosure: prepared with AI assistance; I verified both reproductions, the stdlib differential and
the red/green runs myself.

Seek with io.SeekEnd computed Len()-off, so a negative offset moved past
the end instead of before it and later reads returned zeros. ReadInt24
converted a 24-bit value straight to int32, which cannot carry the sign
the way the int8/16/32/64 siblings do.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@youdie006