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

symbols fail on Windows when there are non-ascii characters in the MemProcFS path. #255

Closed
dongdun opened this issue Dec 27, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@dongdun
Copy link

dongdun commented Dec 27, 2023

1

Not only this problem, I feel that many of my files have not been read. Compared with others, other people's txt files have content, while many of mine are empty files.

my system is win11

@ufrisk
Copy link
Owner

ufrisk commented Dec 27, 2023

Have you copied the latest binaries from https://github.com/ufrisk/MemProcFS/releases/tag/v5.8 and unzipped all files in the folder you wish to use.

netstat is sometimes reliant on symbols which are updated each path tuesday by me or downloaded from Microsoft (but you'd need all the DLL files in that download for it to work).

Please let me know if this resolved your issue.

@dongdun
Copy link
Author

dongdun commented Dec 28, 2023

Have you copied the latest binaries from https://github.com/ufrisk/MemProcFS/releases/tag/v5.8 and unzipped all files in the folder you wish to use.

netstat is sometimes reliant on symbols which are updated each path tuesday by me or downloaded from Microsoft (but you'd need all the DLL files in that download for it to work).

Please let me know if this resolved your issue.

  1. I copied all the MemProcFS folders installed in Win11 to another Win10 computer, which means that the files are the same. After the Win10 computer executes, the content of netstat can be seen.

  2. And my Win11 error is indeed a symbol related issue, but as mentioned earlier, the MemProcFS files are all the same, so I am not sure if it is a problem with the Win11 basic environment or if some files of Win11 were called that I do not have.

Initialized 64-bit Windows 10.0.22621
[SYMBOL] Functionality may be limited. Extended debug information disabled.
[SYMBOL] Offline symbols unavailable - file 'info.db' not found.
[SYMBOL] Reason: Unable to download kernel symbols to cache from Symbol Server.

============================== MemProcFS ==============================

@dongdun
Copy link
Author

dongdun commented Dec 28, 2023

Have you copied the latest binaries from https://github.com/ufrisk/MemProcFS/releases/tag/v5.8 and unzipped all files in the folder you wish to use.

netstat is sometimes reliant on symbols which are updated each path tuesday by me or downloaded from Microsoft (but you'd need all the DLL files in that download for it to work).

Please let me know if this resolved your issue.

Sorry, I found the problem. The installation path of my MemprocFS contains Chinese characters, which causes the program to not execute normally.
For now, just cancel the Chinese characters path.

@dongdun dongdun closed this as completed Dec 28, 2023
@ufrisk ufrisk changed the title Why doesn't my netstat -v show anything? symbols fail on Windows when there are non-ascii characters in the MemProcFS path. Dec 28, 2023
@ufrisk ufrisk added the bug Something isn't working label Dec 28, 2023
@ufrisk
Copy link
Owner

ufrisk commented Dec 28, 2023

I'm reopening the issue, I'll look into to see if I can fix this. If there are issues with the libraries used I might not be able to, but it would be nice to have it working with non-ascii characters.

Thanks for reporting and finding out about this issue 👍

@ufrisk ufrisk reopened this Dec 28, 2023
@ufrisk
Copy link
Owner

ufrisk commented Mar 3, 2024

This bug should now be resolved. Symbols should now work in directories with non-ascii characters. Can you please verify.

@ufrisk ufrisk closed this as completed Mar 3, 2024
@dongdun
Copy link
Author

dongdun commented Mar 4, 2024

I downloaded the latest version for verification and it has been resolved。

这个错误现在应该已经解决了。符号现在应该可以在包含非 ASCII 字符的目录中使用。能否请您核实一下。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants