ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] 1.3.3 - "proto_register_field_array" crashes with type "FT_B

From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Thu, 4 Feb 2010 19:27:01 +0100

Well, go ahead and create such a page under /Development


Send from my iPhone

On 4 feb 2010, at 18:01, Beth <beth.tridium@xxxxxxxxx> wrote:

It seems I'm not the only one who got bitten by this change (several times - I'm a slow learner). 

Just wondering, is there a "troubleshooting" wiki somewhere that collects this sort of knowledge?  I'd love to see something organized by the many mysterious compile or execution failure messages, with likely trouble sources for each.  So when you get the inevitable "Runtime exception" popup with no further explanation, at least you have someplace to look it up, with a list of possible goofs to look for in your code.

And perhaps it would ease the frustration of the developers who uncover these issues, knowing they have someplace to report it where it will help others avoid the same difficulty.

On Thu, Feb 4, 2010 at 10:40 AM, Bill Meier <wmeier@xxxxxxxxxxx> wrote:

Change the BASE_HEX to BASE_NONE.

Non-numeric types (FT_STRING, FT_BYTES, etc) now require BASE_NONE.

Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>