|RE: [dsdp-dd-dev] Is there any need for a multi-Container MIimplementation?|
Le lundi 17 mars 2008 à 15:02 -0400, Marc Khouzam a écrit : > > What I'd like to discuss in this mail is the other part of the > > modifications we did to support our usage. In a nutshell, a lot of > > components assume that there's only one Container context (ie. only one > > debugger), which isn't true for us. I was wondering if there might be > > general interest in patches that introduces awareness of multiple > > top-level contexts. > > >From an Ericsson perspective, we do have interest in multiple top-level > contexts. We are not quite there yet, but will need to tackle this problem > in the coming month or two. So, at least for me, I would appreciate > seeing what you have done for this support. I can try to cleanup one of our hacks and post it. For example the CommandCache modifications. It's no rocket science and I think the abstraction might not be the right one if we want to share the code with another different usage scenario, but it's a start. To be more specific, we have multiple Container contexts and thus choose to store per-ContainerContext state. If you would like to use a similar mechanism to handle thread specific state (as GDB won't be globally running or stopped), you'd need to store per-ExecutionContext state. > Integrating this in DSF is another question though, as there is some work > being done there (although it is currently on hold.) So, I will leave it > to more knowlegeable people than I, to address this question. I'm a bit confused now. Are you speaking about integrating non-stop thread debugging into DSF or something else? When you expressed your interest in multiple top-level contexts above, was it wrt a single GDB in non-stop mode or maybe multiple GDBs in the same session? Just to be sure what we're discussing... Fred.
Back to the top