Wireshark mailing list archives
Re: Debugging an assertion failure
From: Michael Mann <mmann78 () netscape net>
Date: Fri, 14 Apr 2017 07:56:45 -0400
There were a lot of suggestions on how to break on the failure point (which I can't help with), but if you just go to the line it complains about (it's slightly different in the master branch I have), you come up with: * Make sure that only lower-case ASCII letters, numbers, * underscores, hyphens, and dots appear in the name. * * Crash if there is, as that's an error in the code; * you can make the title a nice string with capitalization, * white space, punctuation, etc., but the name can be used * on the command line, and shouldn't require quoting, * shifting, etc. So I would say the issue is that you have a invalid character in your preference name or description. -----Original Message----- From: Paul Offord <Paul.Offord () advance7 com> To: Developer support list for Wireshark <wireshark-dev () wireshark org> Sent: Fri, Apr 14, 2017 6:42 am Subject: [Wireshark-dev] Debugging an assertion failure Hi, 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 == '.') This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. If I remove the dissector the problem goes away and so I’m sure it’s the cause. Even though I can recreate the problem in a debug build under VS 2013 it doesn’t catch the exception. I just see the above text flash by in the output command box. How can I cause execution to break when it throws the exception? Thanks and regards…Paul ______________________________________________________________________ This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ ___________________________________________________________________________ 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
___________________________________________________________________________ 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
Current thread:
- Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Ahmad Fatoum (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Ahmad Fatoum (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Graham Bloice (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Graham Bloice (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Michael Mann (Apr 14)
- Re: Debugging an assertion failure Maynard, Chris (Apr 14)
- Re: Debugging an assertion failure Anders Broman (Apr 14)
- Re: Debugging an assertion failure Guy Harris (Apr 14)
- Re: Debugging an assertion failure Guy Harris (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 14)
- Re: Debugging an assertion failure Paul Offord (Apr 15)
- Re: Debugging an assertion failure Guy Harris (Apr 14)
- Re: Debugging an assertion failure Ahmad Fatoum (Apr 14)