If you use VS these are some good ideas on how to debug better. Unless you don't need no stinkin debuggin
https://blogs.msdn.microsoft.com/visualstudio/2017/06/26/7-lesser-known-hack...
Always use printf() and "?" kind of tools to debug.
On Thu, Jun 29, 2017 at 4:12 AM, Stephen Russell srussell705@gmail.com wrote:
If you use VS these are some good ideas on how to debug better. Unless you don't need no stinkin debuggin
I like the conditional if for a breakpoint.
On Thu, Jun 29, 2017 at 7:54 AM, Man-wai Chang changmw@gmail.com wrote:
Always use printf() and "?" kind of tools to debug.
On Thu, Jun 29, 2017 at 4:12 AM, Stephen Russell srussell705@gmail.com wrote:
If you use VS these are some good ideas on how to debug better. Unless
you
don't need no stinkin debuggin
-- .~. Might, Courage, Vision. SINCERITY! / v \ 64-bit Fedora 25 Server Spin /( _ )\ http://sites.google.com/site/changmw ^ ^ May the Force and farces be with you!
[excessive quoting removed by server]
I never needed a debugger for VS... ;)
On Thu, Jun 29, 2017 at 5:32 PM, Stephen Russell srussell705@gmail.com wrote:
I like the conditional if for a breakpoint.
On Thu, Jun 29, 2017 at 7:54 AM, Man-wai Chang changmw@gmail.com wrote:
Always use printf() and "?" kind of tools to debug.
On Thu, Jun 29, 2017 at 4:12 AM, Stephen Russell srussell705@gmail.com wrote:
If you use VS these are some good ideas on how to debug better. Unless
you
don't need no stinkin debuggin
-- .~. Might, Courage, Vision. SINCERITY! / v \ 64-bit Fedora 25 Server Spin /( _ )\ http://sites.google.com/site/changmw ^ ^ May the Force and farces be with you!
[excessive quoting removed by server]