| Re: [platform-debug-dev] New Register's view doesn't ask my registers to compute a detail value |
When the method gets passed an IRegisterGroup selection it ignores it and returns. It is not a big thing, just that in the Variables view all things (because they are all IVariables) can show something in the details pane.
Alan Boxall - IBM Distributed Debugger
platform-debug-dev-admin@xxxxxxxxxxx wrote on 05/06/2004
03:05:47 PM:
> Sorry, I've just seen these postings... What do you mean by "will
> not get a value from an IRegisterGroup"?
>
> Mikhail Khodjaiants
> QNX Software Systems
> ----- Original Message -----
> From: Alan Boxall
> To: platform-debug-dev@xxxxxxxxxxx
> Sent: Thursday, May 06, 2004 2:13 PM
> Subject: Re: [platform-debug-dev] New Register's
view doesn't ask my
> registers to compute a detail value
>
>
> Good news! I debugged the core debugger code and found that
the
> problem was in my code. I was not returning the proper model
> presentation ID.
>
> But I did notice that in the following code I can't get detail for
a
> register group. The code that has ">" will not
get a value from an
> IRegisterGroup
>
> Just want to know if this was by design or just because it was
> inherited from the Variables view?
>
> if (!selection.isEmpty()) {
> IValue val = null;
> Object obj = selection.getFirstElement();
> if (obj instanceof IndexedVariablePartition)
{
> // no details
for parititions
> return;
> }
> > if (obj instanceof IVariable) {
> > val =
((IVariable)obj).getValue();
> > } else if (obj instanceof IExpression)
{
> > val =
((IExpression)obj).getValue();
> > }
> > if (val == null) {
> > return;
> > }
> // workaroud for bug 12938
> if (fValueSelection != null &&
fValueSelection.equals(selection)) {
> return;
> }
>
> setDebugModel(val.getModelIdentifier());
> fValueSelection = selection;
> fSelectionIterator = selection.iterator();
> fSelectionIterator.next();
> fLastValueDetail= val;
> getModelPresentation().computeDetail(val,
this);
> }
>
>
> Alan Boxall - IBM Distributed Debugger