Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Alexey Neyman <avn@xxxxxxxxxxxxxxx>
Date: Sun, 3 Aug 2008 14:02:56 -0700

On Sunday 03 August 2008 12:05:33 Guy Harris wrote:
> 	-fwrapv
> 		This option instructs the compiler to assume that signed arithmetic
> overflow of addition, subtraction and multiplication wraps around
> using twos-complement representation. This flag enables some
> optimizations and disables others. This option is enabled by default
> for the Java front-end, as required by the Java language
> specification.
>
> We only run on two's-complement platforms, as far as I know (no
> Univac mainframes run Wireshark, as far as I know), so, unless signed
> arithmetic overflow causes a trap, addition and subtraction
> presumably wrap around.  Does turning that option on fix this
> problem?

Yes, it does.

Best regards,
Alexey Neyman.

  • References:
    • [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
      • From: Alexey Neyman
    • Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
      • From: Alexey Neyman
    • Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
      • From: Guy Harris
  • Prev by Date: Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
  • Next by Date: Re: [Wireshark-dev] tshark-1.0.2 (dumpcap) signal abort core saved, see the stack-trace, any help please.
  • Previous by thread: Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
  • Next by thread: Re: [Wireshark-dev] Memory corruption on x86_64 / GCC 4.2.3
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation