| Re: [cdt-dev] General API to retreive a Memory Block from different targets |
Hi Jonah, Thanks a lot for your answers. The DSF tutorials helped me to understand the concepts of DSF. I finally end up with something that works: for a remote GDB server (e.g, in Qemu) I am able to retrieve a memory block with a specific start address and size. As my code needed to be synchronous I indeed used a Query. Your pointers were really helpful. However, In the process I realized that TCF is not using DSF. I found some documentation about a project that try to connect DSF and CDT but it seems deprecated. To avoid duplication of code I wonder if I should use the Eclipse Platform Debug APis directly, or something in CDT. Because right now I cannot use DMContexts from DSF as TCF implements its own mechanism. Do you have an idea what I could look at? Thanks again, Alexis From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Jonah Graham Hi Alexis, The DSF asynchronous model is somewhat unique. You are on the correct track - but you shouldn't be creating the services yourself, but instead obtaining them from the service tracker. To learn DSF programming model have a look at the DSF tutorial at https://help.eclipse.org/2020-09/topic/org.eclipse.cdt.doc.isv/guide/dsf/intro/dsf_programming_intro.html?cp=15_0_6 The IMemoryDMContext can't generally be retrieved with an adapter call. Use DMContexts.getAncestorOfType. For example if your dmc is a frame context (most common type of selection in the Debug view) then it's parent is an execution context representing a thread, and its parent is a container context representing a process. In the standard gdb use case, the container ancestor is also a memory context (because each process has its own view of memory). So, something like IMemoryDMContext memContext = DMContexts.getAncestorOfType(dmc, IMemoryDMContext.class). Then you can use the executor that you obtained (your exec variable) to execute async operations on the memory service you have obtained from the service tracker (don't forget to dispose it) that you can create like this: tracker = new DsfServicesTracker(YOURPLUGIN.getBundleContext(), session.getId()); If your calling code needs to be synchronous you can run your operation in a Query - but be careful of concurrency rules in the link. I hope that has been helpful. Please ask follow up questions. DSF is very powerful, but also quite complicated to go with that power. Jonah On Thu, 19 Nov 2020 at 09:24, Alexis Bouffies <Alexis.Bouffies@xxxxxx> wrote:
|