Microsoft Technology Licensing, LLC

Ian H Carmichael

Christopher Wellington Brumme

Sean Edwin Trowbridge

Patrick Henri Dussud

Mahesh Prakriya

WeiWen Liu

Michael M Magruder

Beysim Sezgin

Brian M Grunkemeyer

Peter Alan Carlin

Steven J Pratschner

Mason K Bendixen

Lawrence B Sullivan

Li Zhang

Vance Palmer Morrison

Raja Krishnaswamy

David N Cutler

Christopher David Brown

James S Miller

Jonathan White Keljo

Brian Robert Crawford

John Lawrence Hamby

Peter A Hallam

Brian D Harry

Alan C Shi

James H Hogg

Jason L Zander

Sam Spencer

William G Evans

Sean Selitrennikoff

John Joseph Rivard

James J Radigan

Scott D Mosier

Suzanne Maurine Cook

Douglas Jay Rosen

Steven J Steiner

Mei-Chin Tsai

Mario Chenier

Jennifer A Hamilton

Habib Heydarian

In an exemplary media implementation, one or more electronically-accessible media include electronically-executable instructions that utilize an application programming interface, the application programming interface facilitating creation of callback-type dynamic function tables; each callback-type dynamic function table including a begin address, an end address, and a callback function, each callback-type dynamic function table corresponding to a code heap that stores code for multiple functions in a runtime environment; wherein interaction between the runtime environment and an operating system is precipitated upon calling the callback function to acquire exception handling and/or unwind information. In another exemplary media implementation, one or more electronically-accessible media include at least part of an operating system that is configured to request from a runtime environment exception handling and/or unwinding information for functions that are managed by the runtime environment.

Operating system managing a linked list of callback dynamic function tables for acquiring exception handling information from a runtime environment

A finalizer may include a notification that no tolerance for failure or corruption is expected. Any potential failure point, which may be induced by a runtime execution environment routine or subroutine that is associated with the finalizer may then be prepared apart from the finalizer.

Critical finalizers

The techniques and mechanisms described herein are directed to a method for virtually catching an exception. A debugger receives a notification identifying information about an exception that occurred during execution of an application. The debugger then selectively chooses a location on a call stack where execution of the application resumes after the stack is unwound up to the selected location. The location being between a statement on the stack causing the exception and a handler on the stack. The handler being identified during a search phase for exception processing. The mechanism being operative for both handled exceptions and unhandled exceptions.

System and method for virtual catching of an exception

A system and method of providing edit and continue support in a software program debugging environment. 'Edit and continue' support allows a user (e.g., programmer and/or developer) to update the code and/or data structure(s) of an executing program while it is running. After the user has finished editing their code and resumes execution, an integrated development environment (IDE) propagates the edit(s) into a common language runtime (CLR) environment before continuing. Therefore, from the CLR environment's perspective, an edit is a block of intermediate language code (IL) and/or metadata that is inserted into a running process. Moreover, The IDE can facilitate: determining 'legality' of an edit; building the edit; sending the edit to the CLR environment; and/or, facilitating the CLR environment switch execution to the edited code.

Method and system for program editing and debugging in a common language runtime environment

Deterministic code execution may be recovered for programs or portions thereof by implementing a programmable policy on a system host to escalate the scope of a code discard based on various parameters.

Execution recovery escalation policy

Systems and methods for enhanced runtime hosting are described. In one aspect the runtime hosting interface includes a host abstraction interface. The HAI allowing the runtime to configure host execution environment parameters and/or notify the host of a runtime event. In particular, the host abstraction interface (HAI) corresponds to execution environment abstractions supported by a host application. Responsive to an action or event, the runtime invokes an identified HAI or an associated object during execution of runtime managed code.

Runtime hosting interfaces

Systems and methods for enhanced runtime hosting are described. In one respect, the runtime identifies any abstraction interface(s) exposed by a host application. The abstraction interface(s) correspond to respective execution environment functionality implemented by the hosting application. During execution of runtime managed code and responsive to an action or event associated with an identified one of the respective execution environment abstractions, the runtime calls a specific interface or object corresponding to a specific one of the abstraction interface(s). This allows the host application to customize/enhance its execution environment, which includes the runtime, as a function of the implemented abstraction(s).

Enhanced runtime hosting

Growing community of inventors

Sammamish, WA, United States of America

Ian H Carmichael