[vim/vim] Memory leak with :breakadd expr (PR #18844)

7 views
Skip to first unread message

zeertzjq

unread,
Dec 1, 2025, 1:57:52 AM (2 days ago) Dec 1
to vim/vim, Subscribed

Problem: Memory leak with :breakadd expr.
Solution: Free debug_oldval and debug_newval before assigning to them.

It seems that :breakadd expr doesn't work as documented at all. This PR
only fixes the memory leak. The tests are for the existing behavior.


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/18844

Commit Summary

  • 8473a9c Memory leak with :breakadd expr

File Changes

(2 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18844@github.com>

zeertzjq

unread,
Dec 1, 2025, 2:13:53 AM (2 days ago) Dec 1
to vim/vim, Push

@zeertzjq pushed 1 commit.

  • 93449e4 Memory leak with :breakadd expr


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18844/before/8473a9c812b028c93d6264757237d258a298a4a2/after/93449e42cf54ab52e93b037ccea2ff43cb991181@github.com>

Christian Brabandt

unread,
Dec 1, 2025, 2:29:49 PM (2 days ago) Dec 1
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#18844)

Thanks, the memory leak is my fault I guess. I remember some wonky behavior when implementing the expr part of it. Seems like it is not much used really.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18844/c3598496819@github.com>

Christian Brabandt

unread,
Dec 1, 2025, 2:50:35 PM (2 days ago) Dec 1
to vim/vim, Subscribed

Closed #18844 via a474de6.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/18844/issue_event/21286129880@github.com>

Reply all
Reply to author
Forward
0 new messages