Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] RE: Fixing some Debug feature-parity bugs

I've made a wiki page to track this effort.
It can be found at CDT Wiki -> Component Documentation -> DSF-GDB feature parity effort (under debug)

or directly at: http://wiki.eclipse.org/CDT/cdt-debug-feature-parity-effort

Believe it or not, 19 bugs have already been taken and only 13 left!
Who else wants to be part of this community effort?

I'm very impressed by the CDT community!!!

Thanks

Marc

________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: February 6, 2010 8:55 PM
To: CDT DEV (cdt-dev@xxxxxxxxxxx)
Subject: [cdt-dev] FW: [cdt-debug-dev] Fixing some Debug feature-parity bugs

>From Marc-Andre Laperle  (forwarded from cdt-debug-dev which I posted the orginal by mistake)

Great idea about the wiki, I will create one.
As for documentation, yes there is some for DSF, but to be honnest, it's been so long since I looked
at it that I don't know where the latest doc is.  Maybe someone else can answer better than me?

Thanks Marc-Andre!

________________________________________
From: cdt-debug-dev-bounces@xxxxxxxxxxx [cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc-Andre Laperle [malaperle@xxxxxxxxxxxxx]
Sent: February 6, 2010 2:02 PM
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Fixing some Debug feature-parity bugs

Hi,

I'm still pretty new to DSF and DSF-GDB but I want to help so I'll pick
the what looks like the easier ones. I'll try to do:

http://bugs.eclipse.org/274951 [cdi] Add Watch action to C/C++ Editor
http://bugs.eclipse.org/269927 [console] [cdi] Allow to save console to
a file

I will also look at any bugs on Mac that might come up. Maybe we should
have a wiki page with who is trying to fix what? Also, is there any
documentation on DSF/DSF-GDB that could help me getting more familiar
with the framework?

Thanks!

Marc-Andre

On 10-02-05 5:25 PM, Pawel Piech wrote:
> I've really enjoyed following this discussion and seeing the
> enthusiasm around DSF and TCF out there.  There is a few issues that
> I've been meaning to get to ever since we introduced DSF.  I'll do my
> best to get them in for Helios:
>
> 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/269101 [variables][cdi] In no-columns mode,
> it's impossible to change the a variable's value.
> http://bugs.eclipse.org/219203 [variables][cdi] Variables view should
> allow variables to be cast to a type.
> http://bugs.eclipse.org/219202 [variables][cdi] Variables view should
> use icons to represent types.
> http://bugs.eclipse.org/248627 [debug view] [cdi] Add an option to
> show full paths for the stack frame source location.
> http://bugs.eclipse.org/159958 [symbols][cdi] Integrate symbols
> service with CDT modules view.
>
>
> Cheers,
> Pawel
>
>
> Marc Khouzam wrote:
>> Hi,
>>
>> 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
>> with CDI-GDB.
>>
>> 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
>> Signals view.
>> 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?
>>
>> Marc
>> _______________________________________________
>> cdt-debug-dev mailing list
>> cdt-debug-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top