Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tcf-dev] reduced getState function
Hi David,

imho with these patches tcf clients might end up with different states for the same context.

I have not tried your patches but if you do the following:
1) Connect with Eclipse and insert and hit a breakpoint
2) Connect a 2nd time with Eclipse

With your patches applied, do you see the same state in Eclipse with the two connections? My guess is that the 2nd connection does not show the breakpoint hit.

 - Sanimir


On Tue, May 25, 2021 at 1:04 PM Wilson, David <david.wilson@xxxxxxxxx> wrote:

Hi Eugene,

 

Sorry to ask again, I was wondering if you have had a chance to look over my email from 19/5/2021? The email is as follows:

 

--- original message ---

Hi All –

 

We are having an issue at TCF protocol level relating to performance on Systems which have many Contexts.

 

The issue relates to the getState command being called on all contexts, which in turn, triggers a read on the program counter (pc) register.

 

On systems with a large number of contexts (especially over real hardware with JTAG), this has a massive performance penalty.

 

Now, we have seen several types of target where we can infer the state (i.e. has a breakpoint been hit, is it suspended etc) WITHOUT reading the PC. We would still like to show the “State” to the user, and thus have come up with a getMinState solution (detailed https://git.eclipse.org/r/c/tcf/org.eclipse.tcf.agent/+/172121) and GUI patch (https://git.eclipse.org/r/c/tcf/org.eclipse.tcf/+/175151)

 

Eugene Tarassov very kindly provided me with another potential solution to this, by not intercepting contexts. This would not require any code change. Unfortunately, is not an acceptable solution for us, as it does not allow us to provide the user with all the information we “know” – i.e. have the contexts been suspended or not. Eugene suggested “suspended, intercepted, but not active", which I can’t figure out how to trigger from the tcf agent (where we need this behaviour to come from) – simply setting this as “not active” from the client also seems cumbersome and unintuitive for a end user. Hence it seems the current approaches will not work to fix this issue.

 

Any help with our particular problem would be greatly appreciated.

---end of original message---

 

 

This is a completely blocking issue for us, and one that we believe other TCF developers and users will also encounter.

 

Any help/comments would be greatly appreciated.

 

Kind Regards

 

David Wilson

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tcf-dev

Back to the top