KubaO / KubaO/pole

Some file entries are wrongly read as 0 length in OLE file created on Windows

Open
#1 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

*Imported issue. Reporter: Jacob Lorensen*
*Note: The ole file has been zipped - GitHub doesn't support raw attachments of this type*

Attached screenshots of OLE file opened with poleview shows that two of the files (_component.int and _composite.int) are wrongly read as 0-length files.

I bisected and found that the original changeset is correct, and the bug is introduced in commt 30cf6b0

This does not happen with all Windows OLE files. So far I have found this one example, attached too.
![file-good-cset-0](https://user-images.githubusercontent.com/5444571/83074474-3a9de980-a040-11ea-9870-64d5b4e78890.png)
![file-bad-cset-1](https://user-images.githubusercontent.com/5444571/83074480-3e317080-a040-11ea-9900-36b18e0a8e2d.png)
[ole.ole.zip](https://github.com/KubaO/pole/files/4691969/ole.ole.zip)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the report with the attached ole.ole.zip and inspecting how _component.int and _composite.int are read around regression commit 30cf6b0. Compare behavior with the preceding changeset and add a regression check showing that both entries retain their correct lengths.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.