Re: [cdt-debug-dev] Adding a Target....

[Chris Songer <songer@xxxxxxxxxxxxx>]

<laugh> In the end I ended up having to do both.

The target command was moved to createLaunchSession. But I still had to 
hook restart in CTarget because the default implementation was destructive 
for our target and because restart looks very architecture specific for us. 
For it's something like: set $pc = ResetVector; set $cacheattr = 
defaultCacheattr (and you don't want to know what it looks like on configs 
with MMUs.)

So good suggestion Alain, that is the right place to add the MI target 
send. It's just too bad I have to have that CTarget subclass anyway to do 
those other things.

Thanks!
-Chris

At 12:49 PM 1/25/2003 -0800, Chris Songer wrote:

> > I'm not sure about one thing, the extension of cdi.CTarget, could you
> > not just attach to the target when you were creating the session in
> > XtGDB.createCSession() ?
>
> Assuming I understand the question: Yes you could as long as no one else 
> is invoking restart.
>
> I thought of that, but I didn't because of personal ignorance. There's a 
> lot of code that I don't know. Sending an exec-run to our the MP simulator 
> after attaching is bad and that means restart() in CTarget was destructive 
> if it got invoked. I was not clear what menu item or other thing might get 
> a hold of the target and send a restart and was I concerned that just 
> attaching in the session would leave some hole.
>
> If restart will only ever be called by the createCSession call, or resume 
> under createCSession, then that's a much better way to do it.
>
> Thanks!
> -Chris
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev