[cdt-dev] FW: [cdt-debug-dev] Fixing some Debug feature-parity bugs
>From John Cortell (forwarded from cdt-debug-dev which I posted the orginal by mistake)
From: cdt-debug-dev-bounces@xxxxxxxxxxx [cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell [rat042@xxxxxxxxxxxxx]
Sent: February 5, 2010 2:41 PM
To: CDT Debug developers list; 'CDT Debug developers list'
Subject: Re: [cdt-debug-dev] Fixing some Debug feature-parity bugs
Grabbing the bull by the horns may be exactly what we need here.
You've thankfully taken the initiative to pull together the punch
list; now we just need people to dive in and help you tackle it. I've
gotten approval from management to commit some time to the cause.
I'll take the following four issues, and will begin after I'm done
with the DSF disassembly view work.
http://bugs.eclipse.org/248606 [menu][breakpoints][cdi] Add support
for toggling watchpoints in the variables and expressions views.
http://bugs.eclipse.org/248595 [breakpoints][cdi] - Add support
pending breakpoints introduced in GDB 6.8.
http://bugs.eclipse.org/249220 [signals][cdi] Add support for the Signals view.
http://bugs.eclipse.org/248627 [debug view] [cdi] Add an option to
show full paths for the stack frame source location.
At 01:13 PM 2/5/2010, Marc Khouzam wrote:
>recent email discussions about the CDT's default debugger integration
>has led to the fact that it would be nice to switch the default to
>DSF-GDB for Helios, but that we need to get closer to feature-parity
>We also agree that new debugging features are not going to be
>done for CDI, so I think we need to start building momentum for DSF-GDB
>so as to get more contributions and get the whole CDT debugging to continue
>getting more new features. This will also benefit any DSF-based integration
>as DSF will be given more attention.
>So, let's take the bull by the horns and get some feature-parity bugs fixed.
>The bugzilla list of 29 bugs is shown below, taken from http://bit.ly/avphMO
>If we want to actually see some progress, we need people to reply to this mail
>an agree to take care of some bugs, even if only a single one to start.
>I'll get the ball rolling by committing to fix the following 7 bugs myself:
>http://bugs.eclipse.org/242943 [breakpoints] [cdi] While GDB is
>running, we cannot make breakpoint commands
>http://bugs.eclipse.org/248610 [menu][memory][cdi] Add a menu action
>to open memory view for a given variable.
>http://bugs.eclipse.org/249162 [run control][cdi] Add support for
>"Set PC to here" operation.
>http://bugs.eclipse.org/249165 [run control][cdi] Add support for
>"Resume at Line" action
>http://bugs.eclipse.org/249169 [detail][cdi] Add support for
>alternative expression evaluation in detail pane.
>http://bugs.eclipse.org/219203 [variables][cdi] Variables view
>should allow variables to be cast to a type.
>http://bugs.eclipse.org/202354 [launch][cdi] Support Environment tab
>in local launch
>These as the other filled bugs about feature-parity that others
>should look at:
>http://bugs.eclipse.org/248587 [breakpoints][cdi] Support "Event' Breakpoints.
>http://bugs.eclipse.org/248606 [menu][breakpoints][cdi] Add support
>for toggling watchpoints in the variables and expressions views.
>http://bugs.eclipse.org/248595 [breakpoints][cdi] - Add support
>pending breakpoints introduced in GDB 6.8.
>http://bugs.eclipse.org/231883 [console][cdi] Inferior does not
>print to console when a PTY is not available
>http://bugs.eclipse.org/159958 [symbols][cdi] Integrate symbols
>service with CDT modules view.
>http://bugs.eclipse.org/235747 [registers][cdi] Allow user to edit
>the register groups.
>http://bugs.eclipse.org/237560 [variables][cdi] Ehance variables
>view for feature parity with CDT.
>http://bugs.eclipse.org/248593 [launch][cdi] Add a JTAG-specific launch.
>http://bugs.eclipse.org/249220 [signals][cdi] Add support for the
>http://bugs.eclipse.org/249223 [signals][cdi] Add support for
>"Resume without signal" action.
>http://bugs.eclipse.org/274951 [cdi] Add Watch action to C/C++ Editor
>http://bugs.eclipse.org/248627 [debug view] [cdi] Add an option to
>show full paths for the stack frame source location.
>I believe the ones below are not show-stoppers and therefore lower
>priority, but not everyone may agree with this:
>http://bugs.eclipse.org/264895 [console][cdi] Visible console should
>match debug selection
>http://bugs.eclipse.org/207582 [variables][expressions][cdi] In
>views, chirldren of arrays should be grouped when more than 100
>http://bugs.eclipse.org/219040 [variables][cdi] Variables view
>should show globals (or should it?)
>http://bugs.eclipse.org/219202 [variables][cdi] Variables view
>should use icons to represent types.
>http://bugs.eclipse.org/267209 [launch][cdi] Refresh project when
>launch process terminates
>http://bugs.eclipse.org/269101 [variables][cdi] In no-columns mode,
>it's impossible to change the a variable's value.
>http://bugs.eclipse.org/271795 [debug view] [cdi] Inferior should be
>visible, and shown terminated in post mortem launch
>http://bugs.eclipse.org/293832 [variables][cdi] wrong display of
>variable values with GDB DSF
>http://bugs.eclipse.org/300096 [expressions][run control][cdi] DSF
>is missing certain debug actions from editor's context menu
>http://bugs.eclipse.org/269927 [console] [cdi] Allow to save console to a file
>Who's up for the challenge?
>cdt-debug-dev mailing list
cdt-debug-dev mailing list