-
Notifications
You must be signed in to change notification settings - Fork 28
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
investigate how to run gdb server inside QM #719
Comments
However, I would like to merge after mr. @rhatdan review it. |
We do not want to allow this inside of QM by default. This would allow the one QM Process to read data within another QM process and even modify it. Why would anyone be running a database in production? Why wouldn't you run the gdb from the host ASIL environment? |
Agreed, we need to explain customers to use ASIL not QM. QM is just a process inside the host that gdb can attach. |
To my knowledge the QM partition is a separate pid namespace which means I can not attach to the process I am trying to debug. If I understand correctly I would need to run gdb in there which brings me back to my original problem of how to debug an application in-situ within the QM partition using gdbserver. |
Just because it is in a pid namespace does not mean that it can not see the process or ptrace it. You can also do a |
But thats exactly where I get the selinux denials as shown in #719 (comment)
I wonder if |
Based in the logs @raballew provided: #718
The text was updated successfully, but these errors were encountered: