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

Timeout commands #34

Open
enlight opened this issue Sep 25, 2015 · 0 comments
Open

Timeout commands #34

enlight opened this issue Sep 25, 2015 · 0 comments

Comments

@enlight
Copy link
Owner

enlight commented Sep 25, 2015

I've run into an issue with lldb-mi on Windows (though my Ubuntu VM fares no better) where attempting to connect to a remote target that is unreachable results in lldb-mi just sitting there forever without responding to anything. Arguably this is a bug in lldb-mi (or maybe lldb itself, or the host-only VirtualBox network driver) but dbgmits should be able to recover from this sort of situation by terminating the lldb-mi process and throwing a suitable error if a response is not received within a reasonable amount of time. The amount of time a command is expected to take may differ from one command to the next, so it should be possible to specify the timeout value per command, however for ease of use there should be a way to specify a default timeout for certain categories of commands.

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

No branches or pull requests

1 participant