public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA 0/9] Radically simplify the complaint system
Date: Mon, 28 May 2018 22:19:00 -0000	[thread overview]
Message-ID: <87tvqrxwon.fsf@tromey.com> (raw)
In-Reply-To: <bdf607ba-9c0d-1b60-f02d-9c9e6c34d29a@redhat.com> (Pedro Alves's	message of "Mon, 28 May 2018 19:57:36 +0100")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

[ QUIT ]
Pedro> And then when that happens, 'complaints.c'::series is not
Pedro> restored back [because the clear_complaints call is skipped,
Pedro> because it is not exception safe], so all the following
Pedro> complaints are issued with SHORT_FIRST_MESSAGE:

Hah, oops.  I have a series now to remove SHORT_FIRST_MESSAGE.  It still
won't be perfect here -- there's no cleanup object still and so you
could in theory see too many complaints if you C-c at the wrong time.
I don't think that is super important though.

Pedro> I guess I just see complaint output similar to "set debug foo" output,
Pedro> where I also wish we were more consistent in printing some leading
Pedro> prefix for each debug knob, like, "set debug infrun 1" producing
Pedro> output messages prefixed with "infrun:" or something like that.

This makes sense to me too.  I was tempted to just remove it entirely,
but it is nice to be able to throttle the messages, since ordinarily
there are many of the same kind in a given objfile.

Pedro> Not sure what you mean here.  I was just thinking of something like
Pedro> simply making sure to include "DWARF reader:" in all complaint calls in
Pedro> dwarf2read.c.

Ok, I see.  I thought you meant something where symfile would tell the
complaints system about the module in question.

Tom

  reply	other threads:[~2018-05-28 22:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  5:09 Tom Tromey
2018-05-22  5:07 ` [RFA 2/9] Remove elements from complaint_series Tom Tromey
2018-05-22  5:07 ` [RFA 9/9] Remove struct complaints Tom Tromey
2018-05-22  5:08 ` [RFA 6/9] Remove vcomplaint Tom Tromey
2018-05-22  5:08 ` [RFA 5/9] Remove struct explanation Tom Tromey
2018-05-22  5:09 ` [RFA 4/9] Remove symfile_complaints Tom Tromey
2018-05-22  5:09 ` [RFA 8/9] Remove struct complain Tom Tromey
2018-05-22  5:09 ` [RFA 1/9] Remove internal_complaint Tom Tromey
2018-05-22  5:50 ` [RFA 3/9] Remove "noisy" parameter from clear_complaints Tom Tromey
2018-05-22  7:01 ` [RFA 7/9] Remove file and line from struct complain Tom Tromey
2018-05-23 14:49 ` [RFA 0/9] Radically simplify the complaint system Pedro Alves
2018-05-23 15:08   ` Tom Tromey
2018-05-23 17:44     ` Pedro Alves
2018-05-28 10:41       ` Tom Tromey
2018-05-28 10:41         ` Tom Tromey
2018-05-28 19:37         ` Pedro Alves
2018-05-28 22:19           ` Tom Tromey [this message]
2018-05-29 16:05             ` Pedro Alves
2018-06-04 20:25 ` Possible regression on gdb.gdb/complaints.exp (was: Re: [RFA 0/9] Radically simplify the complaint system) Sergio Durigan Junior
2018-06-04 21:38   ` Possible regression on gdb.gdb/complaints.exp Tom Tromey
2018-06-04 23:29     ` Sergio Durigan Junior

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=87tvqrxwon.fsf@tromey.com \
    --to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).