[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cdt-dev] Conf. call details about bug 88546 - "Serious issues while debugging in Remote Development scenario"
- From: Sumit Sarkar <sumit.sarkar@xxxxxxxxx>
- Date: Wed, 23 Mar 2005 18:13:52 -0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=bxwj3aamZciBXriQlox5zb02FayLE46VRrcdctR3dX0k7sPSAfNAd3k97KOX2C+C4W//kOrr6z9+bNfodtEIuhJdaw0h1kSrBiyImw+E0gdS27a/m+CyR4gpyap6zig7hdIZRiVPiHDgU9O5l2IQrKK5Kz7JfCsJT+eKKG8vZWQ=
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)
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
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.
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