[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] DSF-GDB feature-parity status
|
This does not sound good.
As soon as you have the bug with the traces, I'll have a look.
don't forget to mention your platform and gdb version
Thanks
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Axel Müller
> Sent: Tuesday, February 16, 2010 10:10 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] DSF-GDB feature-parity status
>
> I notice the same behavior when I manually add a breakpoint
> when the program
> is halted (by another breakpoint). GDB eats all the cpu power
> and does not
> respond to any Eclipse commands.
> In addition, I am not able to set a new breakpoint when the
> program is already
> running!
> As I mentioned before, this does not happen with the CDI debugger.
>
> Am Dienstag, 16. Februar 2010 16:02:34 schrieb Axel Müller:
> > This option was disabled. I just jumped 3 lines ahead and
> there were only
> > statements. No function calls. The cpu load of GDB went up
> during this time
> > to nearly 100%.
> > I also tried a small simple program. There it worked like a charm.
> >
> > > Did you set the option to skip breakpoints when running to line?
> > > If so, are you running over a method that has a
> breakpoint set in it?
> > > That will slow down the operation a lot.
> > >
> > > That behavior has been annoyting me too. I have a couple
> of ideas.
> > > Can you just confirm this is your case and if so, open a bug
> > > to track it?
> > >
> > > Thanks
> > >
> > > > -----Original Message-----
> > > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Axel Müller
> > > > Sent: Tuesday, February 16, 2010 9:38 AM
> > > > To: CDT General developers list.
> > > > Subject: Re: [cdt-dev] DSF-GDB feature-parity status
> > > >
> > > > Marc,
> > > >
> > > > I just played around with DSF debugging in the current
> HEAD version.
> > > > The RunToLine feature works in principle. However, it is
> > > > horrible slow. It
> > > > takes more than 10(!) seconds when I select a line and then
> > > > press CTRL-R until
> > > > the debugger arrives at the line. At first, I was thinking it
> > > > did not work and
> > > > pressed the key binding several times. The standard (CDI)
> > > > debugger needs less
> > > > than 1 second (same machine and application) for the
> same operation.
> > > > BTW, I am using GDB 7.0 (Ubuntu Karmic).
> > > >
> > > > Axel
> > > >
> > > > Am Montag, 15. Februar 2010 02:00:56 schrieb Marc Khouzam:
> > > > > Hi all,
> > > > >
> > > > >
> > > > >
> > > > > Here's the status of the DSF-GDB feature-parity effort
> > > >
> > > > after one week.
> > > >
> > > > > I've added a 'Bugs completed' section to the wikipage:
> > > > > http://wiki.eclipse.org/CDT/cdt-debug-feature-parity-effort
> > > > >
> > > > >
> > > > >
> > > > > Out of a total of 40 bugs to fix to reach CDI-feature-parity
> > > > >
> > > > >
> > > > >
> > > > > 8 bugs have been completed
> > > > > 21 have been assigned to someone
> > > > > 11 are yet to be assigned
> > > > >
> > > > >
> > > > >
> > > > > I think this is very encouraging and I hope to see more
> > > >
> > > > bugs disappearing
> > > >
> > > > > as the days go by.
> > > > >
> > > > >
> > > > >
> > > > > Things that are now available in HEAD are:
> > > > >
> > > > > - RunToLine, MoveToLine and ResumeAtLine are all supported
> > > >
> > > > (including the
> > > >
> > > > > DSF-Disassembly view) - Fixed the use of run control
> > > >
> > > > commands from the gdb
> > > >
> > > > > console
> > > > > - Details of variables as well as pretty-printing (when
> > > >
> > > > available) are now
> > > >
> > > > > being displayed
> > > > >
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > >
> > > > > Marc
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > cdt-dev mailing list
> > > > > cdt-dev@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > >
> > > > _______________________________________________
> > > > cdt-dev mailing list
> > > > cdt-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > > _______________________________________________
> > >
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>