Wireshark mailing list archives
Re: Does proto_deregister_field really work?
From: Peter Wu <peter () lekensteyn nl>
Date: Sun, 27 May 2018 12:19:49 +0200
Hi Richard, On Wed, May 09, 2018 at 04:51:13PM -0700, Richard Sharpe wrote:
Hi folks, I have an application where I want to change the specification of an HF entry or two, and found proto_deregister_field. It would seem that I can deregister a field and then register a new version of it ... as long as I am careful. What is the cost of doing this? Is an alternative to register a fixed array but modify the entries?
What was the use case for this dynamic field update? What property were you interested in? I am not sure how well dynamic field (de)registration is supposed to work. It is causing some memory leaks and I am worried that trying to solve those can result in other memory safety issues (use-after-free). -- Kind regards, Peter Wu https://lekensteyn.nl ___________________________________________________________________________ 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:
- Does proto_deregister_field really work? Richard Sharpe (May 09)
- Re: Does proto_deregister_field really work? Peter Wu (May 27)
- Re: Does proto_deregister_field really work? Richard Sharpe (May 28)
- Re: Does proto_deregister_field really work? Paul Offord (May 28)
- Re: Does proto_deregister_field really work? Guy Harris (May 28)
- Re: Does proto_deregister_field really work? Richard Sharpe (May 28)
- Re: Does proto_deregister_field really work? Peter Wu (May 27)