Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't send queries to the MI interpreter
Date: Fri, 10 Feb 2017 19:30:00 -0000	[thread overview]
Message-ID: <aa355e7b-7d31-83fd-1530-b580a06f3274@redhat.com> (raw)
In-Reply-To: <71cf7c59-8b3c-595d-b4ec-69f44ae3d6fc@ericsson.com>

On 02/10/2017 07:05 PM, Simon Marchi wrote:
> 
> Note that we can trigger the same bug you mentioned higher with pagination.  For
> example, I have a huge list of breakpoints and I do "info break" on UI #1 then on
> UI #2.

I assume you mean that on UI #2 you do the same.

> Pressing enter on UI #1 unblocks UI #2, and the following enter crashes
> GDB.  So should we also say that pagination is only allowed on the main UI for the
> same reasons?

Yes, I think so.  The branch disabled it too, see filtering_enabled.

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-02-10 19:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 16:37 Simon Marchi
2017-02-10 16:48 ` Pedro Alves
2017-02-10 16:52   ` Simon Marchi
2017-02-10 17:12     ` Pedro Alves
2017-02-10 17:44       ` Pedro Alves
2017-02-10 18:07         ` Pedro Alves
2017-02-10 18:36           ` Pedro Alves
2017-02-10 19:08             ` Simon Marchi
2017-02-10 19:23               ` Pedro Alves
2017-02-10 19:06           ` Simon Marchi
2017-02-10 19:20             ` Pedro Alves
2017-02-10 19:26               ` Simon Marchi
2017-02-10 19:32                 ` Pedro Alves
2017-02-10 19:30             ` Pedro Alves [this message]
2017-02-10 19:03         ` Simon Marchi
2017-02-10 19:08           ` Pedro Alves

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=aa355e7b-7d31-83fd-1530-b580a06f3274@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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