diff options
author | Tom Tromey <tom@tromey.com> | 2018-05-16 22:23:09 -0600 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2018-05-23 09:16:59 -0600 |
commit | 43ba33c7689a9eeb20a3c36ecb9867574963ee0e (patch) | |
tree | 6b1acffd6809b7d4afe92ed366b9f6f360b81267 /gdb/complaints.c | |
parent | 2b9496b2b4781b21bc30a70337e24205f8a923d8 (diff) | |
download | gdb-43ba33c7689a9eeb20a3c36ecb9867574963ee0e.zip gdb-43ba33c7689a9eeb20a3c36ecb9867574963ee0e.tar.gz gdb-43ba33c7689a9eeb20a3c36ecb9867574963ee0e.tar.bz2 |
Remove elements from complaint_series
I couldn't find a way to get complaints to use a couple of cases, and
the difference between the actual printed output for these cases was
minimal anyway. So, this patch removes a couple of constants from
complaint_series, plus the associated code.
gdb/ChangeLog
2018-05-23 Tom Tromey <tom@tromey.com>
* complaints.c (enum complaint_series): Remove FIRST_MESSAGE,
SUBSEQUENT_MESSAGE.
(vcomplaint, clear_complaints): Update.
(symfile_explanations): Remove some messages.
gdb/testsuite/ChangeLog
2018-05-23 Tom Tromey <tom@tromey.com>
* gdb.gdb/complaints.exp (test_serial_complaints): Remove.
(test_short_complaints): Update.
Diffstat (limited to 'gdb/complaints.c')
-rw-r--r-- | gdb/complaints.c | 60 |
1 files changed, 3 insertions, 57 deletions
diff --git a/gdb/complaints.c b/gdb/complaints.c index 9e5df39..71d36e6 100644 --- a/gdb/complaints.c +++ b/gdb/complaints.c @@ -29,17 +29,9 @@ enum complaint_series { /* Isolated self explanatory message. */ ISOLATED_MESSAGE, - /* First message of a series, includes an explanation. */ - FIRST_MESSAGE, - /* First message of a series, but does not need to include any sort of explanation. */ SHORT_FIRST_MESSAGE, - - /* Subsequent message of a series that needs no explanation (the - user already knows we have a problem so we can just state our - piece). */ - SUBSEQUENT_MESSAGE }; /* Structure to manage complaints about symbol file contents. */ @@ -82,8 +74,6 @@ static struct complain complaint_sentinel; static struct explanation symfile_explanations[] = { { "During symbol reading, ", "." }, - { "During symbol reading...", "..."}, - { "", "..."}, { "", "..."}, { NULL, NULL } }; @@ -169,10 +159,7 @@ vcomplaint (struct complaints **c, const char *file, if (complaint->counter > stop_whining) return; - if (info_verbose) - series = SUBSEQUENT_MESSAGE; - else - series = complaints->series; + series = complaints->series; /* Pass 'fmt' instead of 'complaint->fmt' to printf-like callees from here on, to avoid "format string is not a string literal" @@ -194,16 +181,13 @@ vcomplaint (struct complaints **c, const char *file, { std::string msg = string_vprintf (fmt, args); wrap_here (""); - if (series != SUBSEQUENT_MESSAGE) - begin_line (); + begin_line (); /* XXX: i18n */ fprintf_filtered (gdb_stderr, "%s%s%s", complaints->explanation[series].prefix, msg.c_str (), complaints->explanation[series].postfix); - /* Force a line-break after any isolated message. For the - other cases, clear_complaints() takes care of any missing - trailing newline, the wrap_here() is just a hint. */ + /* Force a line-break after any isolated message. */ if (series == ISOLATED_MESSAGE) /* It would be really nice to use begin_line() here. Unfortunately that function doesn't track GDB_STDERR and @@ -215,19 +199,6 @@ vcomplaint (struct complaints **c, const char *file, } } - switch (series) - { - case ISOLATED_MESSAGE: - break; - case FIRST_MESSAGE: - complaints->series = SUBSEQUENT_MESSAGE; - break; - case SUBSEQUENT_MESSAGE: - case SHORT_FIRST_MESSAGE: - complaints->series = SUBSEQUENT_MESSAGE; - break; - } - /* If GDB dumps core, we'd like to see the complaints first. Presumably GDB will not be sending so many complaints that this becomes a performance hog. */ @@ -264,33 +235,8 @@ clear_complaints (struct complaints **c, int less_verbose, int noisy) p->counter = 0; } - switch (complaints->series) - { - case FIRST_MESSAGE: - /* Haven't yet printed anything. */ - break; - case SHORT_FIRST_MESSAGE: - /* Haven't yet printed anything. */ - break; - case ISOLATED_MESSAGE: - /* The code above, always forces a line-break. No need to do it - here. */ - break; - case SUBSEQUENT_MESSAGE: - /* It would be really nice to use begin_line() here. - Unfortunately that function doesn't track GDB_STDERR and - consequently will sometimes supress a line when it - shouldn't. */ - fputs_unfiltered ("\n", gdb_stderr); - break; - default: - internal_error (__FILE__, __LINE__, _("bad switch")); - } - if (!less_verbose) complaints->series = ISOLATED_MESSAGE; - else if (!noisy) - complaints->series = FIRST_MESSAGE; else complaints->series = SHORT_FIRST_MESSAGE; } |