Skip to content

multi_buffer: Assert char boundary for panic due to point_to_buffer_offset - #40777

Merged
smitbarmase merged 1 commit into
mainfrom
multi-buffer-assert-char-boundary
Oct 21, 2025
Merged

multi_buffer: Assert char boundary for panic due to point_to_buffer_offset#40777
smitbarmase merged 1 commit into
mainfrom
multi-buffer-assert-char-boundary

Conversation

@smitbarmase

@smitbarmase smitbarmase commented Oct 21, 2025

Copy link
Copy Markdown
Member

In an attempt to figure out what's wrong with point_to_buffer_offset for crash #40453. We want to know which branch among these two is the bad one.

Release Notes:

  • N/A

Co-authored-by: Lukas Wirth <lukas@zed.dev>
@cla-bot cla-bot Bot added the cla-signed The user has signed the Contributor License Agreement label Oct 21, 2025
@zed-industries-bot

Copy link
Copy Markdown
Contributor
Messages
📖

This PR includes links to the following GitHub Issues: #40453
If this PR aims to close an issue, please include a Closes #ISSUE line at the top of the PR body.

Generated by 🚫 dangerJS against d5e08b1

@smitbarmase smitbarmase changed the title multi_buffer: Assert char boundary for more info on crash multi_buffer: Assert char boundary for panic due to point_to_buffer_offset Oct 21, 2025
@smitbarmase
smitbarmase merged commit 10b9ae5 into main Oct 21, 2025
24 checks passed
@smitbarmase
smitbarmase deleted the multi-buffer-assert-char-boundary branch October 21, 2025 13:31
jolutz pushed a commit to jolutz/zed that referenced this pull request Aug 8, 2026
…ffset (zed-industries#40777)

In an attempt to figure out what's wrong with `point_to_buffer_offset`
for crash zed-industries#40453. We want to
know which branch among these two is the bad one.

Release Notes:

- N/A

Co-authored-by: Lukas Wirth <lukas@zed.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants