Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
	        Pedro Alves <pedro@codesourcery.com>,
	        "gdb-patches\@sourceware.org"
	<gdb-patches@sourceware.org>,
	        Joel Brobecker <brobecker@adacore.com>,
	        Michael Snyder <msnyder@vmware.com>
Subject: Re: Another proposal for frontends and queries.
Date: Wed, 16 Sep 2009 18:03:00 -0000	[thread overview]
Message-ID: <m3ab0urcnc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <daef60380909160717h7da7e1b5k7b7db285a64f1877@mail.gmail.com> 	(Hui Zhu's message of "Wed, 16 Sep 2009 22:17:05 +0800")

>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:

>> And about the patch I said can handle this issue is "set record query
>> <on|off>" patch.  I cannot find who don't like this patch.

I don't like it, I think I said that in another thread.

The reason I don't like it is twofold.

First, queries are a general feature of gdb.  They are sprinkled about
rather liberally.  So, if one causes problems for a front end, then it
probably represents a general class of problems.  IMO, fixing it in this
ad hoc way is not a good way to attack a generic problem.

The thought experiment to perform here is to consider generalizing this
solution to all the queries in gdb.  I think that would result in
madness: hundreds of "disable this query" settings.

Second, this has the feeling of an "unbreak my gdb" option.  That is,
setting an option to avoid one particular query says to me that the
query is probably badly chosen in some way.

Tom


  parent reply	other threads:[~2009-09-16 18:03 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14  2:38 Marc Khouzam
2009-09-14  6:45 ` Vladimir Prus
2009-09-14 13:07   ` Marc Khouzam
2009-09-14 14:09 ` Joel Brobecker
2009-09-14 14:28   ` Marc Khouzam
2009-09-14 14:48     ` Pedro Alves
2009-09-14 14:57       ` Marc Khouzam
2009-09-14 15:08       ` Joel Brobecker
2009-09-14 15:36         ` Marc Khouzam
2009-09-14 16:06           ` Joel Brobecker
2009-09-15 16:26         ` Joel Brobecker
2009-09-16  6:24           ` Hui Zhu
2009-09-16 12:38             ` Marc Khouzam
2009-09-16 13:06               ` Hui Zhu
2009-09-16 13:25                 ` Pedro Alves
2009-09-16 13:46                   ` Hui Zhu
2009-09-16 13:59                     ` Marc Khouzam
2009-09-16 14:17                       ` Hui Zhu
2009-09-16 14:26                         ` Joel Brobecker
2009-09-16 14:34                           ` Hui Zhu
2009-09-16 14:45                             ` Pedro Alves
2009-09-16 14:43                           ` Marc Khouzam
2009-09-16 18:03                         ` Tom Tromey [this message]
2009-09-16 23:36                           ` Hui Zhu
2009-09-16 23:40                             ` Joel Brobecker
2009-09-16 17:12                   ` Eli Zaretskii
2009-09-14 15:23     ` Joel Brobecker
2009-09-16 20:20     ` Tom Tromey
2009-09-16 20:35       ` Marc Khouzam
2009-09-17  0:17         ` Michael Snyder
2009-09-17  0:48           ` Marc Khouzam
2009-09-17  1:03             ` Joel Brobecker
2009-09-17  2:07               ` Marc Khouzam
2009-09-17  0:16       ` Michael Snyder
2009-09-16 20:43 ` Tom Tromey
2009-09-16 21:41   ` Joel Brobecker
2009-09-17 13:51     ` Marc Khouzam
2009-09-17 19:52       ` Tom Tromey
2009-09-18  4:59         ` Hui Zhu
2009-09-18  5:16           ` Michael Snyder
2009-09-18  9:31           ` Pedro Alves
2009-09-18 14:37             ` Joel Brobecker
2009-09-18 14:57         ` Marc Khouzam
2009-09-18 16:42           ` Tom Tromey
2009-09-22  0:46             ` Marc Khouzam
2009-09-22 22:49               ` [RFA/commit] s/nquery/query/ in record.c (was "Re: Another proposal for frontends and queries.") Joel Brobecker
2009-09-23 12:45                 ` Marc Khouzam
2009-09-24  3:05                   ` Hui Zhu
2009-09-24 17:59                 ` Joel Brobecker

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=m3ab0urcnc.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=teawater@gmail.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