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

Deadlocks when debugging ThreadSendValues and ThreadReceiveValues #211

Open
TanYuzhen opened this issue Sep 19, 2024 · 0 comments
Open

Deadlocks when debugging ThreadSendValues and ThreadReceiveValues #211

TanYuzhen opened this issue Sep 19, 2024 · 0 comments

Comments

@TanYuzhen
Copy link

TanYuzhen commented Sep 19, 2024

Hello, author.
I'm debugging ABYcore and I'm running the PerformInteraction() function when two Parties interact. However, when I debug with gdb, I use the gdb command set schedule-locking on for the purpose of switching to the Client for receiving after the Server performs sending. Similarly, I want the Client to send and then the Server to receive.
Unfortunately, after I do this, the program deadlocks. Can you tell me why?
Because when I debug this part, if I don't execute this gdb command, only one of the two functions ThreadSendValues() and ThreadReceiveValues() can be debugged, and even if the other one adds a breakpoint in it, it is executed immediately, and I can't catch it.
In other words, I can't properly debug both functions ThreadSendValues() and ThreadReceiveValues() in a single participant, gdb is only able to catch one function and the other is executed automatically. Can you please tell me how I can solve this problem.
Looking forward to your reply!
1726739099020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant