Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vectorstream: support file sizes larger than INT_MAX #191

Merged
merged 1 commit into from
Jul 6, 2024

Conversation

grrtrr
Copy link
Contributor

@grrtrr grrtrr commented Jan 9, 2023

File sizes larger than INT_MAX cause segmentation faults, due to the use of pbump/gbump, which only support int increments.

Rewrite int-based offset adjustments to use streamoff offsets instead.

Fixes #190.

File sizes larger than INT_MAX cause segmentation faults, due to the use
of `pbump/gbump`, which only support `int` increments.

Rewrite `int`-based offset adjustments to use streamoff offsets instead.

Fixes boostorg#190.
@igaztanaga igaztanaga merged commit 480bd01 into boostorg:develop Jul 6, 2024
@igaztanaga
Copy link
Member

Many thanks!

igaztanaga added a commit that referenced this pull request Jul 6, 2024
@grrtrr grrtrr deleted the issue_190 branch July 7, 2024 13:47
Sign up for free to 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.

[vectorstream] basic_vectorbuf segmentation fault when exceeding INT_MAX elements
2 participants