Hi Marc,
Thanks for the info ! I see that the startup sequences of the services determines the order they receive the events. That’s certainly good to know, though it is not enough for my case. What I want is actually
to wait for all debugger views (variables, registers, memory, etc) to finish updating after each stepping before I do my snapshot capturing.
Ling
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Marc Khouzam
Sent: Monday, August 05, 2013 10:38 AM
To: 'CDT General developers list.'
Subject: Re: [cdt-dev] DSF: do sth. after stepping is done
The DSF events are sent to listener with a certain ordering, as defined in DsfSession.doDispatchEvent() (look at the overridden compare() method in there).
Events are first sent to all dsf services that care about that event, then to other listeners. Dsf services receive the events in order, based on their startup
sequence.
I'm not sure if that will be sufficient for you though...
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ling Wang
Sent: Friday, August 02, 2013 11:00 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] DSF: do sth. after stepping is done
Hi DSF gurus,
In EDC, we have a good feature of taking snapshot of the program/device status after each stepping. Basically it stores some memory data, register values etc. in a file. We do by in handling the ISuspendedDMEvent. But you know, the handlers
for the ISuspendedDMEvent are not invoked in a specific order. So the memory stored in my snapshot may not be the latest data. Is there a way for me to make sure that my task is done after all other handlers are finished ?
I see the class SteppingController that can help me ensure no stepping is started before my snapshot taking is finished. But I don’t see that it can help me on the above mentioned issue.
Thanks for any pointer !
Ling
