aboutsummaryrefslogtreecommitdiffstats
path: root/wiretap/wtap.c
diff options
context:
space:
mode:
authorGuy Harris <guy@alum.mit.edu>2011-12-13 09:53:50 +0000
committerGuy Harris <guy@alum.mit.edu>2011-12-13 09:53:50 +0000
commitd94bd07f99438278cb11f24b00571ab2907b6bdb (patch)
tree5f96d0a35c97af466bcb2d5b8a9371327bb0190f /wiretap/wtap.c
parent1df4ee91090e35c25835204d7175b9395be32606 (diff)
Rename WTAP_ERR_BAD_RECORD to WTAP_ERR_BAD_FILE; it really reports any
form of corruption/bogosity in a file, including in a file header as well as in records in the file. Change the error message wtap_strerror() returns for it to reflect that. Use it for some file header problems for which it wasn't already being used - WTAP_ERR_UNSUPPORTED shouldn't be used for that, it should only be used for files that we have no reason to believe are invalid but that have a version number we don't know about or some other non-link-layer-encapsulation-type value we don't know about. svn path=/trunk/; revision=40175
Diffstat (limited to 'wiretap/wtap.c')
-rw-r--r--wiretap/wtap.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiretap/wtap.c b/wiretap/wtap.c
index 464023103b..530a573f86 100644
--- a/wiretap/wtap.c
+++ b/wiretap/wtap.c
@@ -605,7 +605,7 @@ static const char *wtap_errlist[] = {
NULL,
NULL,
"Less data was read than was expected",
- "File contains a record that's not valid",
+ "The file appears to be damaged or corrupt.",
"Less data was written than was requested",
"Uncompression error: data oddly truncated",
"Uncompression error: data would overflow buffer",