Wireshark mailing list archives
Re: Error in Wireshark (tshark.c:646)
From: Guy Harris <guy () alum mit edu>
Date: Thu, 20 Apr 2017 10:01:32 -0700
On Apr 20, 2017, at 5:05 AM, Pascal Quantin <pascal.quantin () gmail com> wrote:
Short answer: it will not as it will create other errors:
But "const char *volatile exp_pdu_filename = NULL" should work - it's not what exp_pdu_filename points to that needs to be made volatile, it's the pointer *itself* that needs to be made volatile. Done in https://code.wireshark.org/review/21248. ___________________________________________________________________________ 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:
- Error in Wireshark (tshark.c:646) Remy Leone (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Pascal Quantin (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Pascal Quantin (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Guy Harris (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Guy Harris (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Pascal Quantin (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Graham Bloice (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Jeff Morriss (Apr 20)
- Re: Error in Wireshark (tshark.c:646) Pascal Quantin (Apr 20)