[vim/vim] Termdebug doesn't work with directories starting with numbers (Issue #19866)

3 views

Skip to first unread message

A. S. Budden

unread,

Mar 30, 2026, 1:41:49 PM (8 days ago) Mar 30

to vim/vim, Subscribed

abudden created an issue (vim/vim#19866)

Steps to reproduce

In a Windows 11 command prompt:

git clone https://github.com/abudden/vim-termdebug-issue-demo
cd vimtermdebug-issue-demo\projects\7600-my-coded-project
g++ -g -o testingtermdebug.cpp testingtermdebug.exe
c:\vim\gvim.exe -u NONE -U NONE testingtermdebug.cpp

In the resulting Vim window:

:packadd Termdebug
:Termdebug testingtermdebug.exe
6gg
:Break

Expected behaviour

Breakpoint should be added and displayed. Breakpoint is added, but Vim can't tell where it is and when you step through the code it doesn't highlight the current line.

If you repeat the test above but replace step 2 with cd vimtermdebug-issue-demo (i.e. omit `projects/7600-my-coded-project), it works as expected (the same file is present in both folders to simplify the demo).

The issue is this line in termdebug.vim (which was presumably put there for a reason so the fix might not be as simple as removing it, although that's what I've done in my local copy).

That line of code modifies gdb-reported filenames by replacing projects\7600-my-coded-project with something like projects\ǰ0-my-coded-project where ǰ is the unicode character with octal value 760. Vim then can't find the file being referenced in the gdb message. I guess this is only an issue on Windows because of the backslashes in paths.

Version of Vim

9.2.0000

Environment

Windows 11 gvim.

Logs and stack traces

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

4:59 AM (17 hours ago) 4:59 AM

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19866)

the problem is the backslash as directory separator on Windows. We had similar issue with the termdebug not recognizing '\t' or '\n'. It will be impossible to make it work, if gdb sends the messages encoded using the \ooo form.