Re: Debugging an assertion failure

[Guy Harris <guy () alum mit edu>]

On Apr 14, 2017, at 3:41 AM, Paul Offord <Paul.Offord () advance7 com> wrote:
 
> I need some advice.  I’m debugging a problem with a dissector I’ve written.  Tshark fails with:
> … \epan\prefs.c:414:prefs_register_module_or_subtree: assertion failed: (g_ascii_islower(c) || g_ascii_isdigit(c) || 
> c == '_' || c == '-' || c == '.')

Your dissector probably has, in its "filter name", a character that is not any of 'a'-'z', '_', '-', or '.'.

NOTE: this means 'A'-'Z' are not valid characters in a filter name.  Be nice to users - don't force them to hold the 
shift key when typing the name of a protocol in, for example, a filter expression.

(And the code has been changed to make this not an assertion; instead, it should now print a message giving the 
offending preference module name.  That fix is in the current master, 2.2, and 2.0 branch; it's not in the current 
2.2.x or 2.0.x release, but will be in the next such release, if and when that comes out.)
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe