-
-
Notifications
You must be signed in to change notification settings - Fork 292
Infrastructure: investigate #7740 #7741
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
base: development
Are you sure you want to change the base?
Infrastructure: investigate #7740 #7741
Conversation
#### Brief overview of PR changes/additions Adds a couple of debug output lines to report the Mudlet application's idea of what it's "current working directory" is immediately prior to running the `TLuaInterpreter::loadGlobal()` method. #### Motivation for adding to Mudlet This is designed to aide in the diagnosis of the issue Mudlet#7740 which only seems to manifest in Release and PTB builds of Mudlet on Windows. #### Other info (issues closed, discussion etc) I think this will be needed to be merging into the development branch - so as to incorporate it into a PTB for testing. It is only a couple of lines and should not interfere with the operation of the code as it only introduces an extra line of text into the debug output each time a profile is (re)loaded. I suspect, but need this to confirm it, that, unlikely as it should be, a particular package seems to be capable of modifying the execution environment of the Mudlet application from a profile's Lua interpreter. This shouldn't be possible, but I am just following up on the pronouncement of the fictional detective *Sherlock Homes*: > "You will not apply my precept," he said, shaking his head. "How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth?" > -- Authur Conan Doyle, *The Sign of the Four*, ch. 6 (1890) Signed-off-by: Stephen Lyons <slysven@virginmedia.com>
Hey there! Thanks for helping Mudlet improve. 🌟 Test versionsYou can directly test the changes here:
|
💡 Actually, since I haven't up dated my MSYS2+Mingw-w64 installation on my Windows Laptop recently I should be able to cherry-pick this PR onto the 4.19.1 code and build a |
is this still required? |
I think we still have the problem although the person who brought it up changed their scripts to be a bit more cautious about using the luafilesystem |
Brief overview of PR changes/additions
Adds a couple of debug output lines to report the Mudlet application's idea of what it's "current working directory" is immediately prior to running the
TLuaInterpreter::loadGlobal()
method.Motivation for adding to Mudlet
This is designed to aide in the diagnosis of the issue #7740 which only seems to manifest in Release and PTB builds of Mudlet on Windows.
Other info (issues closed, discussion etc)
I think this will be needed to be merging into the development branch - so as to incorporate it into a PTB for testing. It is only a couple of lines and should not interfere with the operation of the code as it only introduces an extra line of text into the debug output each time a profile is (re)loaded.
I suspect, but need this to confirm it, that, unlikely as it should be, a particular package seems to be capable of modifying the execution environment of the Mudlet application from a profile's Lua interpreter. This shouldn't be possible, but I am just following up on the pronouncement of the fictional detective Sherlock Homes: