What issues are you facing? I debug O2 code all the time, including profile guided optimised builds as well without too much difficulty. The most common problem is frame pointer omission making local variables and function parameters tough to locate. The /d2Zi+ switch (or /Zo for VS2013 Update 3) can help. See http://randomascii.wordpress.com/2013/09/11/debugging-optimized-codenew-in-visual-studio-2012/ for more info.
On 28 July 2014 13:11, Anders Broman <a.broma...@gmail.com> wrote: > 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? > > Regards > Anders > > ___________________________________________________________________________ > 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-requ...@wireshark.org > ?subject=unsubscribe > -- Graham Bloice Software Developer Trihedral UK Limited
___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe
