{"push_id":2349027873,"size":1,"distinct_size":1,"ref":"refs/heads/fix-preventing-allocation-in-signal-handlers","head":"b19bf60218260f4f969bbf9a33846acf260d616a","before":"95349b6b5b9c639e4a5bbe589f1907113c732ff2","commits":[{"sha":"b19bf60218260f4f969bbf9a33846acf260d616a","author":{"name":"Jan Vorlicek","email":"09bb9bc2e782fb04614d1a465f5dc8996873b58c@microsoft.com"},"message":"Fix preventing memory allocation in signal handler\n\nThere was a subtle bug. When the hardware exception handler returns back\nto the signal handler, the exception's CONTEXT record may contain\nmodified registers and so the changes need to be propagated back to the\nsignal context. But the recent change #16384 was restoring the signal\ncontext from the originally grabbed context instead of the one that's\npointed to by the exception, which is different.\n\nI have also added a little optimization - the contextRecord that was\nadded is not needed, since the signalContextRecord can be used as the\ninitial context record for the exception. So we can save the\ncontextRecord and also copying to the signalContextRecord from it.","distinct":true,"url":"https://api.github.com/repos/janvorli/coreclr/commits/b19bf60218260f4f969bbf9a33846acf260d616a"}]}
{"actor":{"display_login":"janvorli"}}