One Note dump for reference:[Read More]
appverifier lock stops
Reference: AppVerifier Locks
This is more of a dump from various pages of MSDN for handy reference.
A few links i have found useful over time are:[Read More]
debugging library load issues on windows
how to choose stl container
Found somewhere on internet:[Read More]
Last time I coded
peinfo, https://github.com/angeleno/peinfo to get information from a PE file. It listed the guid for pdb file generated alongwith.
This is helpful as it is, but at times you have pdb file and want to query it’s guid.
I did not find anything handy for it, thus ended up coding one myself. Here the Debug Interface Access SDK is of great help.
The idea is pretty simple and straight foward:
- Load PDB as DataSource,
- Open Session,
- Get GlobalScope,
- Get GUID,
adding cmd in visual studio
One of the handy commands with VS IDE is to launch
cmd, it was provided by default earlier but lately i have been missing it with VS 2015 & onwards.
While poking around i found that you could launch
cmd as external tool:
C++11 thread safe statics
My good colleage, Mike.McCarty, put out code for review and stated that statics are thread-safe. As it is, sounded very scary but I trust Mike. Thus started exploring what has been done there.
here is the std document for the same: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2660.htm
First thing wrote some code to dump disassembly in VS2015:[Read More]
github multiple accounts setup notes
key generation and registration
The way github identifies you is thru your ssh keys (public keys need to be registered at github & private keys live on your machine).
The way to generate keys is to find
ssh-keygen, it comes handy with
generating tracebacks for first chance exceptions
Recently I was debugging some workflow where it appeared quite slow. As part of debugging i saw it Visual Studio printed debugging information about first chance exceptions thrown.
Now that David Kline from MS has made it ample clear that FirstChance exceptions are normal exceptions just that debugger gets first chance at them- thus first chance. If debugger chooses not to do anything then application gets a chance to do something about it. If application does not handle it then debugger gets a second chance, thus second chance exceptions. you get the idea.
I have seen lexical_cast being the one that throws exceptions just to parse strings, with xml parsing this could be a big source of exceptions. One of the ways to speed up applications is now to fix or atleast reason about these exceptions being thrown, and having tracebacks makes life lot easier.[Read More]