2004-02-11 00:55:28 +00:00
|
|
|
/* alert_box.c
|
|
|
|
* Routines to put up various "standard" alert boxes used in multiple
|
|
|
|
* places
|
|
|
|
*
|
2004-07-18 00:24:25 +00:00
|
|
|
* $Id$
|
2004-02-11 00:55:28 +00:00
|
|
|
*
|
2006-05-21 05:12:17 +00:00
|
|
|
* Wireshark - Network traffic analyzer
|
|
|
|
* By Gerald Combs <gerald@wireshark.org>
|
2004-02-11 00:55:28 +00:00
|
|
|
* Copyright 1998 Gerald Combs
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
* as published by the Free Software Foundation; either version 2
|
|
|
|
* of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifdef HAVE_CONFIG_H
|
|
|
|
# include "config.h"
|
|
|
|
#endif
|
|
|
|
|
2004-02-21 02:15:07 +00:00
|
|
|
#include <string.h>
|
|
|
|
|
2004-02-11 00:55:28 +00:00
|
|
|
#include <glib.h>
|
|
|
|
|
2004-02-11 01:23:25 +00:00
|
|
|
#include <epan/filesystem.h>
|
2004-02-11 00:55:28 +00:00
|
|
|
#include <epan/dfilter/dfilter.h>
|
|
|
|
|
2012-01-16 03:23:22 +00:00
|
|
|
#include "ui/alert_box.h"
|
2004-02-11 00:55:28 +00:00
|
|
|
|
2012-01-16 03:23:22 +00:00
|
|
|
#include "ui/simple_dialog.h"
|
2004-02-11 00:55:28 +00:00
|
|
|
|
2004-04-16 23:17:13 +00:00
|
|
|
/*
|
|
|
|
* Alert box for general errors.
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
failure_alert_box(const char *msg_format, va_list ap)
|
|
|
|
{
|
|
|
|
vsimple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, msg_format, ap);
|
|
|
|
}
|
|
|
|
|
2004-02-11 01:23:25 +00:00
|
|
|
/*
|
|
|
|
* Alert box for a failed attempt to open or create a file.
|
|
|
|
* "err" is assumed to be a UNIX-style errno; "for_writing" is TRUE if
|
|
|
|
* the file is being opened for writing and FALSE if it's being opened
|
|
|
|
* for reading.
|
|
|
|
*
|
|
|
|
* XXX - add explanatory secondary text for at least some of the errors;
|
|
|
|
* various HIGs suggest that you should, for example, suggest that the
|
|
|
|
* user remove files if the file system is full. Perhaps that's because
|
|
|
|
* they're providing guidelines for people less sophisticated than the
|
2006-05-28 20:28:20 +00:00
|
|
|
* typical Wireshark user is, but....
|
2004-02-11 01:23:25 +00:00
|
|
|
*/
|
|
|
|
void
|
|
|
|
open_failure_alert_box(const char *filename, int err, gboolean for_writing)
|
|
|
|
{
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
|
|
|
file_open_error_message(err, for_writing), filename);
|
|
|
|
}
|
|
|
|
|
2004-02-21 02:15:07 +00:00
|
|
|
/*
|
2004-03-23 21:19:58 +00:00
|
|
|
* Alert box for a failed attempt to read a file.
|
|
|
|
* "err" is assumed to be a UNIX-style errno.
|
2004-02-21 02:15:07 +00:00
|
|
|
*/
|
|
|
|
void
|
2004-03-23 21:19:58 +00:00
|
|
|
read_failure_alert_box(const char *filename, int err)
|
2004-02-21 02:15:07 +00:00
|
|
|
{
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
2004-04-16 23:17:13 +00:00
|
|
|
"An error occurred while reading from the file \"%s\": %s.",
|
2011-06-28 09:00:11 +00:00
|
|
|
filename, g_strerror(err));
|
2004-02-21 02:15:07 +00:00
|
|
|
}
|
|
|
|
|
2004-02-11 01:37:13 +00:00
|
|
|
/*
|
|
|
|
* Alert box for a failed attempt to write to a file.
|
When reporting "sorry, *this* packet can't be written to a file of that
type" when writing out a capture file (i.e., writing a
per-packet-encapsulation capture to a file type that supports it but
doesn't support one of the packet's encapsulations), report the packet
number and, when doing this in a merge operation, report the file from
which it came.
When reporting "sorry, that file can't be written to a file of that
type, period", show the file type rather than the input file link-layer
type that causes the problem. (We could show both. We could be
*really* ambitious and iterate through all possible file types and show
the ones that will or at least might work....)
file_write_error_message() is documented as handling only UNIX-style
errnos, and libwireshark should be usable without libwiretap, so leave
it up to its callers to handle Wiretap errors such as
WTAP_ERR_SHORT_WRITE.
Clean up indentation.
svn path=/trunk/; revision=39949
2011-11-19 20:18:01 +00:00
|
|
|
* "err" is assumed to be a UNIX-style errno if positive and a
|
|
|
|
* Wiretap error if negative.
|
2004-02-11 01:37:13 +00:00
|
|
|
*
|
|
|
|
* XXX - add explanatory secondary text for at least some of the errors;
|
|
|
|
* various HIGs suggest that you should, for example, suggest that the
|
|
|
|
* user remove files if the file system is full. Perhaps that's because
|
|
|
|
* they're providing guidelines for people less sophisticated than the
|
2006-05-28 20:28:20 +00:00
|
|
|
* typical Wireshark user is, but....
|
2004-02-11 01:37:13 +00:00
|
|
|
*/
|
|
|
|
void
|
|
|
|
write_failure_alert_box(const char *filename, int err)
|
|
|
|
{
|
When reporting "sorry, *this* packet can't be written to a file of that
type" when writing out a capture file (i.e., writing a
per-packet-encapsulation capture to a file type that supports it but
doesn't support one of the packet's encapsulations), report the packet
number and, when doing this in a merge operation, report the file from
which it came.
When reporting "sorry, that file can't be written to a file of that
type, period", show the file type rather than the input file link-layer
type that causes the problem. (We could show both. We could be
*really* ambitious and iterate through all possible file types and show
the ones that will or at least might work....)
file_write_error_message() is documented as handling only UNIX-style
errnos, and libwireshark should be usable without libwiretap, so leave
it up to its callers to handle Wiretap errors such as
WTAP_ERR_SHORT_WRITE.
Clean up indentation.
svn path=/trunk/; revision=39949
2011-11-19 20:18:01 +00:00
|
|
|
if (err < 0) {
|
|
|
|
switch (err) {
|
|
|
|
|
|
|
|
case WTAP_ERR_SHORT_WRITE:
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
|
|
|
"A full write couldn't be done to the file \"%s\".",
|
|
|
|
filename);
|
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
|
|
|
"An error occurred while writing to the file \"%s\": %s.",
|
|
|
|
filename, wtap_strerror(err));
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
|
|
|
file_write_error_message(err), filename);
|
|
|
|
}
|
2004-02-11 01:37:13 +00:00
|
|
|
}
|
|
|
|
|
2004-02-11 00:55:28 +00:00
|
|
|
/*
|
|
|
|
* Alert box for an invalid display filter expression.
|
|
|
|
* Assumes "dfilter_error_msg" has been set by "dfilter_compile()" to the
|
|
|
|
* error message for the filter.
|
|
|
|
*
|
|
|
|
* XXX - should this have a "Help" button that pops up the display filter
|
|
|
|
* help?
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
bad_dfilter_alert_box(const char *dftext)
|
|
|
|
{
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK,
|
|
|
|
"%s%s%s\n"
|
|
|
|
"\n"
|
2004-12-29 01:08:20 +00:00
|
|
|
"The filter expression \"%s\" isn't a valid display filter.\n"
|
2004-02-11 00:55:28 +00:00
|
|
|
"See the help for a description of the display filter syntax.",
|
|
|
|
simple_dialog_primary_start(), dfilter_error_msg,
|
|
|
|
simple_dialog_primary_end(), dftext);
|
|
|
|
}
|