For anyone who is unfamiliar with using CodeLLDB on standard VSCode for GNU/Linux, here is the example project, "basicopenslestest", that I used to test the extension:

Project build command:

clang -g -o main main.c -lOpenSLES

main.c

#include <stdio.h>
#include <SLES/OpenSLES.h>

int main(void) {
	SLObjectItf engineObj = NULL;
	SLresult result = slCreateEngine(&engineObj, 0, NULL, 0, NULL, NULL);
	if(result == SL_RESULT_SUCCESS) {
		printf("good\n");
		(*engineObj)->Destroy(engineObj);
		engineObj = NULL;
	}
	else {
		printf("bad\n");
	}
	return 0;
}

.vscode/launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug",
            "program": "${workspaceFolder}/main",
            "args": [],
            "cwd": "${workspaceFolder}"
        }
    ]
}

I noticed that when the update happens, if it was built on a different day/other changes from the previous build, then the installation folder of the previous version will remain "leftover" in the ~/.vscode-oss/extensions/ folder, where it is ignored by the editor in favor of the newer version, and these may build up over time. Simply restarting the editor repeatedly does not seem to trigger cleaning them, at least as far as I can tell.

and removing the if [ "$TERMUX_PACKAGE_FORMAT" = "debian" ] && [ "\$1" != "remove" ] condition from prerm does not prevent that (because --uninstall-extension does not remove the old leftover folder, it just "deactivates" it)

However, if the user clicks this button in the Extensions tab of the editor, then at that moment, the editor immediately "cleans up" all the old, leftover extension folders in ~/.vscode-oss/extensions/, deleting them without deleting any currently-active ones.

This seems like it is just intended behavior, judging from what I see in the issues of VSCode.

• Uninstall extensions won't remove them from disk microsoft/vscode#81046

Some people online say things like "special lldb is required to debug Rust programs with CodeLLDB and my lldb didn't work" (referring to other operating systems, not to this PR), so I have tested to make sure that this build of this extension with lldb from pkg install lldb can debug Rust programs, and as far as I can tell, yes it does work:

After the release of version 1.11.5, I have been able to successfully use the update in Termux.

I believe it is working to the same degree as the previous version, and I have uploaded it here,

however, unfortunately, the upstream code changed significantly, and it was not easy to make the newer version work on Android.

I use this extension, and I think it is very good, but I understand that using a GUI debugger on CLI Android Native programs and/or X11 Android Native programs fully on Android without having any separate computer is a very niche use case, and it is possible that maybe the other users of the code-oss package are only editing projects that run elsewhere, projects that can be debugged without recompiling native code, or native projects without debugging.

I will keep making updates here of each newer version for a while, but if no other people need this extension, it might make more sense for me to only build it locally and use it myself, and might not be needed in the termux-packages repository.