aboutsummaryrefslogtreecommitdiff
path: root/gdb/complaints.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2015-08-06 12:01:05 -0400
committerSimon Marchi <simon.marchi@ericsson.com>2015-08-06 12:01:05 -0400
commit05d999b0896ab6ccd4ce23a715765484c60a967d (patch)
tree66282e3077179b8c79ea5fccc80a776a0bf77f6a /gdb/complaints.c
parentf0ce0d3a331129309a46a6a9ac85fce35acae72b (diff)
downloadgdb-05d999b0896ab6ccd4ce23a715765484c60a967d.zip
gdb-05d999b0896ab6ccd4ce23a715765484c60a967d.tar.gz
gdb-05d999b0896ab6ccd4ce23a715765484c60a967d.tar.bz2
Change type of struct complaints::series
Found while processing the C++ enum changes. It seems like series should be of type enum complaint_series, instead of adding a cast. Redundant and out of date comments are also removed. gdb/ChangeLog: * complaints.c (enum complaint_series): Add newlines and remove out of date comment. (struct complaints) <series>: Change type to enum complaint_series and remove out of date comment. (symfile_complaint_hook): Use equivalent enum value ISOLATED_MESSAGE instead of 0.
Diffstat (limited to 'gdb/complaints.c')
-rw-r--r--gdb/complaints.c17
1 files changed, 5 insertions, 12 deletions
diff --git a/gdb/complaints.c b/gdb/complaints.c
index dbacb2a..b696181 100644
--- a/gdb/complaints.c
+++ b/gdb/complaints.c
@@ -27,18 +27,17 @@ extern void _initialize_complaints (void);
/* Should each complaint message be self explanatory, or should we
assume that a series of complaints is being produced? */
-/* case 1: First message of a series that must
- start off with explanation. case 2: Subsequent message of a series
- that needs no explanation (the user already knows we have a problem
- so we can just state our piece). */
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). */
@@ -69,13 +68,7 @@ struct complaints
{
struct complain *root;
- /* Should each complaint be self explanatory, or should we assume
- that a series of complaints is being produced? case 0: Isolated
- self explanatory message. case 1: First message of a series that
- must start off with explanation. case 2: Subsequent message of a
- series that needs no explanation (the user already knows we have
- a problem so we can just state our piece). */
- int series;
+ enum complaint_series series;
/* The explanatory messages that should accompany the complaint.
NOTE: cagney/2002-08-14: In a desperate attempt at being vaguely
@@ -99,7 +92,7 @@ static struct explanation symfile_explanations[] = {
static struct complaints symfile_complaint_book = {
&complaint_sentinel,
- 0,
+ ISOLATED_MESSAGE,
symfile_explanations
};
struct complaints *symfile_complaints = &symfile_complaint_book;