Re: Debugging an assertion failure

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

On Apr 14, 2017, at 12:41 PM, Guy Harris <guy () alum mit edu> wrote:

> 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 '.'.

No, that's "your *protocol* probably has...", but the code to register a protocol should already be catching that and 
failing.

So perhaps you're directly calling prefs_register_module() and passing it a module name containing a character that's 
not one of those.  Don't do that in a dissector - call prefs_register_protocol(), which uses the protocol's filter name 
as the preferences module name.

___________________________________________________________________________
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