-
Notifications
You must be signed in to change notification settings - Fork 100
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
Using already running qemu #30
Comments
Hi there! If you want to attach to another Qemu instance, you could advice Qemu to spawn a GDBServer as well, and attach to it using the GDBTarget! Just add: If you need access to Qemus QMP, you could set the Monitor protocol of your GDBTarget to qmp. This may work like this (assuming the port for qmp is 9999):
This would require your Qemu instance started with the qmp server: Note that this is not tested and just written from my memory - normally we use the QemuTarget to drive QEMU, and we haven't implemented a |
Thanks for the feedback, I will give it a try! |
As there where no further comments, I'm closing the issue for now. |
Hi Guys,
I try to learn avatar2 in order to analyse IoT software.
My setup, which I set up manually:
I managed to connect to the gdbserver with avatar2, but I wonder how this is the correct way to go.
Is it possible to create a QemuTarget for the already running Qemu process?
Or shall I do something completely different?
Every kind of advice or feedback is welcome :)
Cheers
The text was updated successfully, but these errors were encountered: