Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Conf. call details about bug 88546 - "Serious issue s while debugging in Remote Development scenario"

Done. Updated the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=88546.

Thanks,
sumit


On Thu, 24 Mar 2005 07:00:47 -0500, Thomas Fletcher <ThomasF@xxxxxxx> wrote:
> Can someone dump this information into the bugzilla entry.
> 
> Thanks,
>  Thomas
> 
> > -----Original Message-----
> > From: cdt-dev-admin@xxxxxxxxxxx
> > [mailto:cdt-dev-admin@xxxxxxxxxxx] On Behalf Of Sumit Sarkar
> > Sent: March 23, 2005 9:14 PM
> > To: cdt-dev@xxxxxxxxxxx
> > Subject: Re: [cdt-dev] Conf. call details about bug 88546 -
> > "Serious issues while debugging in Remote Development scenario"
> >
> > Meeting notes from Hewlett-Packard:
> >
> > I agree with Alain. It was very fruitful session.
> >
> > Date/Time: March 22nd 2005, 8:30am PST (11:30am EST)
> > Participants:
> >      Hewlett-Packard (HP):
> >          Alex McKale, Florence Perot, Sumit Sarkar,
> > Balasubramaniyan Krithivasan and Jayaprakash L.V
> >      CDT team from QNX:
> >          Alain Magloire, Dave Inglish and Mikhail Khodjaiants
> >
> > Topic: Discuss about
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=88546
> >
> > 1. "Variables" view:
> >
> >    a) MI command "-var-update *" used to crash cygwin "gdb".
> > But, calling MI command "-var-update *" seems to be working
> > fine for HP gdb in Itanium (HP-UX IA64). It takes less than 2
> > secs to step over to the next line in case of around 70
> > variables. There were no issues filed against HP gdb in this
> > regard. The "Variables" view is getting updated properly.
> >
> >    b) Another way to find the variables in the current
> > context is by calling MI command "-stack-list-locals 1". This
> > MI command emits "name,value" pair of all the variables in
> > the current context. But, it is presented as an array of
> > chars. HP need to parse those "name,value"
> > pairs into meaningful values, so that they can be displayed
> > into the "Variables" tree view.
> >
> >    Next steps: HP will set up a follow up virtual meeting
> > with CDT team in early April, 2005.
> >
> > 2. Registers: HP will wait for the CDT 3.0's implementation
> > of displaying of "selective" registers or register groups.
> >
> > 3. Memory view: HP will test the behavior of the memory view
> > in case of remote development. There is a possibility that
> > the "Memory" view will behave (slow) same as "Registers" view.
> >
> >
> > Thanks,
> > sumit
> >
> >
> >
> > On Tue, 22 Mar 2005 15:59:55 -0500 (EST), Alain Magloire
> > <alain@xxxxxxx> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I have setup a conference call to discuss issue
> > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=88546
> > > >
> > > > Logistics:
> > > > Date: Tuesday, March 22nd 2005
> > > > Time: 8:30am PST ( 11:30am EST)
> > > > Duration: 1 hour
> > > > Dial-in: 1-866-448-1302 (toll-free)
> > > >            1-763-315-6910 (toll)
> > > > Participant id: 4470994#
> > > >
> > > > Agenda:
> > > >    1. Brainstorm the issues listed in the above bug.
> > > >    2. Come up with a solution for future implementation.
> > > >
> > >
> > > Quick followup, for this list.
> > >
> > > It was a very "fructueux"(translation:fruitfull ??) session.
> > >
> > > The scenario: in HP's environment the dialog between gdb is
> > over the net.
> > >
> > > The concerns:  The MI exchange is to verbose and it feels
> > that we can
> > > be more efficient.  a few areas were targeted:
> > >
> > > (1) Variables
> > > (2) Registers
> > > (3) Memory
> > >
> > > (1) Variables: a solution is to use
> > >         -var-update *
> > >     instead of doing for each variables.  Old version of
> > gdb would crash
> > >     if you have a mixed of variables object(Register,
> > variable, memory).
> > >     Action: Look at this again for CDT-3.0.
> > >
> > > (2) Registers:  possible solutions with the coming of RegisterGroups
> > >
> > > (3) Memory:  Possible solutions to use again varobj from GDB, that
> > >     will send us back the diffs instead of fetching the
> > entire memory block
> > >     at each steps.
> > >
> > > to follow this, Sumit will schedule another conf call later.
> > >
> > > Many thanks to the HP folks
> > >
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>


Back to the top