This is the mail archive of the
mailing list for the GDB project.
Re: Using telnet to control a running GDB
- From: Tom Tromey <tromey at redhat dot com>
- To: Marc Khouzam <marc dot khouzam at ericsson dot com>
- Cc: "'Jan Kratochvil'" <jan dot kratochvil at redhat dot com>, "'gdb\ at sourceware dot org'" <gdb at sourceware dot org>
- Date: Tue, 07 Dec 2010 08:51:17 -0700
- Subject: Re: Using telnet to control a running GDB
- References: <F7CE05678329534C957159168FA70DEC572E0C0DCD@EUSAACMS0703.eamcs.ericsson.se> <20101129025627.GA4356@host0.dyn.jankratochvil.net> <F7CE05678329534C957159168FA70DEC572E79C43E@EUSAACMS0703.eamcs.ericsson.se> <20101129185524.GA13721@host0.dyn.jankratochvil.net> <F7CE05678329534C957159168FA70DEC572E79C924@EUSAACMS0703.eamcs.ericsson.se> <email@example.com> <F7CE05678329534C957159168FA70DEC572E0C0DE9@EUSAACMS0703.eamcs.ericsson.se>
>>>>> "Marc" == Marc Khouzam <firstname.lastname@example.org> writes:
Jan> [ You should have more experience with async/non-stop/MI than
Jan> me, though. ]
Marc> We don't always use aync/non-stop in Eclipse. It is up to the
Marc> user to decide.
Tom> I am curious to know why Eclipse works this way.
Marc> From the discussions I have seen about non-stop, it seems some
Marc> user feel the all-stop mode is more intuitive, while others prefer
I am usually confused about all the modes that gdb supports. Your
explanation of non-stop makes sense to me. This has user-visible
effects and could be "weird", especially if you are used to all-stop.
And, I imagine that the reason for not always using async is just that
it isn't universally supported -- you want to handle older GDB versions,
and even with current GDB I suppose it is not supported by all targets.
Is that the situation?
TBH I think it would be better if we could remove some modes. For
example, if we could make target-async either the default, or enabled
automatically if the user uses some async command.