Wireshark mailing list archives
Re: O2 compile option makes it difficult to debug.
From: Bill Meier <wmeier () newsguy com>
Date: Mon, 28 Jul 2014 09:23:31 -0400
Hi, It seems like the O2 option interferes with running the debugger. Would it be better to only use O2 on release builds? I'm not sure how to do that, add nmake -f makefile.nmake release option?
What I've done is to alter config.nmake slightly to allow the specification of WIRESHARK_ENVIRONMENT_CFLAGS as an environment variable the value of which is then added to the end of the CFLAGS (after all the other stuff) in config.nmake.
So: I then set WIRESHARK_ENVIRONMENT_CFLAGS to /OdMy experience has been that the "last seen" value for an option specified multiple times is the one that is used by the 'cl' command (at least for the options I've wanted to override).
If this is considered useful (and not harmful), I can commit the config.nmake change.
Bill ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- O2 compile option makes it difficult to debug. Anders Broman (Jul 28)
- Re: O2 compile option makes it difficult to debug. Graham Bloice (Jul 28)
- <Possible follow-ups>
- Re: O2 compile option makes it difficult to debug. mmann78 (Jul 28)
- Re: O2 compile option makes it difficult to debug. Graham Bloice (Jul 28)
- Re: O2 compile option makes it difficult to debug. Bill Meier (Jul 28)
- Re: O2 compile option makes it difficult to debug. Anders Broman (Jul 28)
