Wireshark-bugs: [Wireshark-bugs] [Bug 4768] Check for max value of range type preference is inco
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4768
--- Comment #3 from Bill Meier <wmeier@xxxxxxxxxxx> 2010-05-16 14:06:43 EDT ---
(In reply to comment #2)
> But how to handle existing out-of-range preference files?
Good question...
g_warning is called with a cryptic "syntax error" message if an out-of-range
preference value is seen when reading the preference file.
(Obviously this can be fixed to generate a better message).
The invalid range preference (actually the complete set of range preferences ?)
is then replaced with the default range preference.
[It also appears that the "reverted" range preference will then be written to
the preferences file (whenever Edit ! Preferences is done ? I haven't dug into
this)].
Unfortunately:
1. On Windows:
The g_warning message will never be seen if the user is running with the
default "never open a console window" preference.
2. On *nix the g_warning message does appear if Wireshark is run from a
command shell.
On my Fedora system when running the standard wireshark as
distributed by Fedora from the Gnome GUI no (g_warning) message appears on
the screen. I haven't figured out if the message is in some log
(and more basically, how the use of stdout/stderr works when a program is
invoked from the Gnome GUI).
To me the way the g_warnings are handled seems a bit less than user-friendly.
What am I missing ?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
