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

Fix copying overlapping buffers in hist_word() #791

Merged
merged 1 commit into from
Aug 16, 2018
Merged

Fix copying overlapping buffers in hist_word() #791

merged 1 commit into from
Aug 16, 2018

Conversation

krader1961
Copy link
Contributor

This came to light as a consequence of @siteshwar adding unit tests for
interactive emacs mode editing behavior.

This came to light as a consequence of @siteshwar adding unit tests for
interactive emacs mode editing behavior.
@siteshwar
Copy link
Contributor

LGTM

@krader1961 krader1961 merged commit 35f67e1 into att:master Aug 16, 2018
@krader1961 krader1961 deleted the overlapped-buffers branch August 28, 2018 22:07
hyenias added a commit to hyenias/ksh that referenced this pull request Mar 20, 2021
While experimenting with ksh93#233, a memory segmentation fault occurred.
A search of other emacs issues found a potential matching issue as
described in att#791. Also, a duplicate
PR of att#1489 was submitted. This
commit backports that fix.

src/cmd/ksh93/edit/history.c: hist_word():
- Switch from using strcpy to memmove as the two strings could overlap.
McDutchie pushed a commit to ksh93/ksh that referenced this pull request Mar 20, 2021
While experimenting with #233, a memory segmentation fault occurred.
A search of other emacs issues found a potential matching issue as
described in att#791. Also, a duplicate
PR of att#1489 was submitted. This
commit backports that fix.

src/cmd/ksh93/edit/history.c: hist_word():
- Switch from using strcpy to memmove as the two strings could overlap.
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.

2 participants