Is there a way to print a stack trace to the debug log from within a function? Sometimes I want to know how I got to a particular dprint or trace message.

long time lurker, first time patcher. core-1151 has a comment added on 2016-02-21 by Radek that page files on drives other than C weren't created. Seemed a good place to start learning the code. This is caused by a hard coded index of 0 in wParam to retrieve the value for DriveIndex so it always get...