new behavior when running "run" command in GDB 8.1 about pygdbmi HOT 3 CLOSED

Thanks for filing, I appreciate it. I will take a look when I get a chance. If you are feeling adventurous, PRs are welcome. But if not that is fine.

from pygdbmi.

Can you add more context on how you are running this? Are you using GdbController? If so, how are you running it? This seems like something you might be able to fix by adjusting your scripts or passing different flags when using the gdb controller. But I might not be understanding.

This documentation may help: https://grassfedcode.com/pygdbmi/api/pygdbmi.html#module-pygdbmi.gdbcontroller

from pygdbmi.

Yes I'm using GdbController, here's my statement:
self.gdbmi = GdbController(gdb_args=['--quiet', '--interpreter=mi2', debugee_name])
and all commands go through the write() function
I've read the doc you provided and tried to adjust time_to_check_for_additional_output_sec to 2 and it works.
I'll try lower it if I have time, 2 sec block is a bit annoying.
Thank you :)

from pygdbmi.