-
Notifications
You must be signed in to change notification settings - Fork 6
Ability to execute in parallel (GDB) #29
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
Ability to execute in parallel (GDB) #29
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have left few queries above. Please have a look at it.
# make sure all output is flushed | ||
# time.sleep(.005) | ||
self.base_gdb_instance.send((("",), {"timeout_sec": 60})) | ||
raw_result += self.base_gdb_instance.recv() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this?
I observed that we do not have this in the run_single_special_command
function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a remaining of the previous efforts to capture GDB response where we listened for stdout output. I think this is no longer needed since we are using the other approach based on the IoManager.
try: | ||
parsed_dict = json.loads(processed_output) | ||
except json.JSONDecodeError: | ||
parsed_dict = processed_output |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is related to the JSONDecodeError
we were talking about.
Without this change, I am getting the JSON error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe there are certain cases where the processed_output is not in the correct format and json.loads fails to parse it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #27
Test with
Previously it would take ~11 secs. Now it takes ~6 secs.