"Well, just read the message, dummy". 8^)
Previously I had initialized everything with zeroes. So the pointers all pointed to zeroes. Setting them to -1 worked. I didn't recognize the ett reference or the significance of the -1 in the error message until I went and looked at the method header. 1.0.3 on registration apparently didn't check for values so zero used to work.
All's well - Wireshark starts up, my preferences dialog is there, and now I can see if the rest works.
Thank you,
Jay Turner
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Thursday, February 10, 2011 2:52 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] tshark run during build with plugins gives register_subtree_array error
On Feb 10, 2011, at 12:38 PM, Turner, Jay wrote:
> Removing the plugins prevented the error. Therefore my plugins must have been starting and they did something wrong. What significantly changed between 1.0.3 plugin initialization and 1.4.3 plugin initialization?
What significantly changed was dissector initialization, whether the dissector is a plugin or not, and the change was that it checks for errors for which it didn't check before the change.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
