-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
sosplugin is not working on ARM #10668
Comments
FYI - Same problem I have on aarch64 using lldb-3.8(armhf) and lldb-3.9(arm64) - i installed both 32 and 64 bit on the same machine just to see if it was a 32bit vs 64bit library loading issue |
@echesakovMSFT |
just a note that it seems to work when I build it my self. (#18827) I'm suspicious this may be build problem . |
I also ended up building lldb5.0.2+sosplugin for arm myself. In my case "official" lldb couldn't even run target process with the following message |
It sounds like there are issues, but is there a process to get to a known working state so I can at least get some deadlock / hang analysis done on Linux Arm32? From what I am reading, if I do the following: Build LLDB 5.0.2? on my 'target' hardware, should I have a working way to do dump analysis? (or attach to a hung process) |
I simply build coreclr with what ever version of lldb you plan to use (5.0 in my case) Also note, that on arm32 you can use Visual Studio for remote debug. |
Issue moved to dotnet/diagnostics dotnet/coreclr#41 via ZenHub |
I tested this in my RP3 as well as Ubuntu on Qemu. I'm not even able to get list of commands.
I did same steps on x64 and lldb-4.0
(lldb) sos
SOS is a debugger extension DLL designed to aid in the debugging of managed
programs. Functions are listed by category, then roughly in order of
...
...
(lldb) sos help
SOS command 'help' not found /home/furt/dotnet-2.1/shared/Microsoft.NETCore.App/2.1.0/libsos.so: undefined symbol: help
The text was updated successfully, but these errors were encountered: