From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] Suppress repeated annotations until GDB is ready to accept input.
Date: Mon, 26 Nov 2012 15:50:00 -0000 [thread overview]
Message-ID: <87vccsics1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20121121201429.1015.6037.stgit@brno.lan> (Pedro Alves's message of "Wed, 21 Nov 2012 20:14:29 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Non-stop or async would complicate this, but no frontend will be
Pedro> using annotations in those modes (one of goes of emacs switching
Pedro> to MI was non-stop mode support, AFAIK).
I've used these modes in Emacs (using M-x gud-gdb) before, and it has
worked ok-enough. Can you say if these patches make it noticeably
worse, or will it be pretty much like it was before?
Tom
next prev parent reply other threads:[~2012-11-26 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50ACF672.7060607@redhat.com>
2012-11-21 20:14 ` [PATCH 0/4] Misc annotations changes Pedro Alves
2012-11-21 20:14 ` [PATCH 2/4] Suppress repeated annotations until GDB is ready to accept input Pedro Alves
2012-11-26 15:50 ` Tom Tromey [this message]
2012-11-26 18:28 ` Pedro Alves
2012-11-27 18:48 ` Tom Tromey
2012-11-27 23:53 ` Pedro Alves
2013-01-22 19:59 ` Pedro Alves
2012-11-27 18:56 ` Eli Zaretskii
2012-11-21 20:14 ` [PATCH 1/4] Remove (alleged) "breakpoints-changed" annotation suppression on ignore count changes Pedro Alves
2012-11-21 20:14 ` [PATCH 4/4] Skip breakpoints-invalid annotations for internal|momentary breakpoints Pedro Alves
2012-11-21 20:14 ` [PATCH 3/4] Fully move the breakpoints-invalid annotation to observers Pedro Alves
2012-11-26 15:23 ` Tom Tromey
2012-11-26 15:42 ` [PATCH 0/4] Misc annotations changes Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vccsics1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox