Abstract: A phasing system for varying a rotational relationship between a first rotary component and a second rotary component includes a gear hub and a cradle rotor. A spider rotor is arranged between the gear hub and the cradle rotor to selectively lock and unlock relative rotation between the gear hub and the cradle rotor. A torsion spring is coupled between the gear hub and the cradle rotor to apply a torque load between the gear hub and the cradle rotor. A planetary actuator is coupled to the gear hub and the spider rotor. The planetary actuator is operable between a steady-state mode, in which relative rotation between the gear hub and the cradle rotor is inhibited, and a phasing mode, in which the planetary actuator receives a rotary input at a predetermined magnitude to selectively provide a relative rotation between the gear hub and the cradle rotor.

Abstract: An expandable interbody device for placement between adjacent vertebrae having an upper structure, a lower structure and a screw mechanism, wherein actuation of the screw mechanism moves the upper and lower structures between a collapsed configuration and an expanded configuration. A deployment tool couples to the expandable interbody device for positioning the device between adjacent vertebrae, actuating the screw mechanism and delivering a material to a chamber of the expandable interbody device.

Abstract: A method of validating a regulated application by generating, on a local data processing system, an automated agent to oversee a validation process of the regulated application on the local data processing system regardless of a local or web-based nature of the regulated application.

Abstract: A program is executed using a call stack and shadow stack. The call stack includes frames having respective return addresses. The frames may also store variables and/or parameters. The shadow stack stores duplicates of the return addresses in the call stack. The call stack and the shadow stack are maintained by, (i) each time a function is called, adding a corresponding stack frame to the call stack and adding a corresponding return address to the shadow stack, and (ii) each time a function is exited, removing a corresponding frame from the call stack and removing a corresponding return address from the shadow stack. A backtrace of the program's current call chain is generated by accessing the return addresses in the shadow stack. The outputted backtrace includes the return addresses from the shadow stack and/or information about the traced functions that is derived from the shadow stack's return addresses.

Abstract: A seal system for a gas turbine engine includes a ceramic matrix composite (CMC) seal arc segment and a carrier supporting the CMC seal arc segment. The CMC seal arc segment defines radially inner and outer sides and has an abradable layer disposed on the radially outer side. There is a cooling cavity radially between the carrier and the abradable layer. The carrier includes a ridge that projects into a groove in the abradable layer and provides a labyrinth seal that partitions the cooling cavity into sub-cavities.

Abstract: A seal system for a gas turbine engine includes a ceramic matrix composite (CMC) seal arc segment and a carrier supporting the CMC seal arc segment. The CMC seal arc segment defines radially inner and outer sides and has an abradable layer disposed on the radially outer side. There is a cooling cavity radially between the carrier and the abradable layer. The carrier includes a ridge that projects into a groove in the abradable layer and provides a labyrinth seal that partitions the cooling cavity into sub-cavities.

Abstract: A flexible plunger rod, drug delivery mechanism, drug delivery device, and methods are described that utilize the flexible plunger rod perform drug delivery operations. In embodiments, the flexible plunger rod can be stored in a curved configuration to thereby reduce a footprint of the drug delivery mechanism and device.

Abstract: Dynamically overriding a function based on a capability set. A computer system reads a portion of an executable image file. The portion includes a first memory address corresponding to a first callee function implementation. The first memory address was inserted into the portion by a compiler toolchain. Based on extensible metadata included in the executable image file, and based on a capability set that is specific to the computer system, the computer system determines a second memory address corresponding to a second callee function implementation. Before execution of the portion, the computer system modifies the portion to replace the first memory address with the second memory address.

Abstract: Dynamically overriding a function based on a capability set. A computer system reads a portion of an executable image file. The portion includes a first memory address corresponding to a first callee function implementation. The first memory address was inserted into the portion by a compiler toolchain. Based on extensible metadata included in the executable image file, and based on a capability set that is specific to the computer system, the computer system determines a second memory address corresponding to a second callee function implementation. Before execution of the portion, the computer system modifies the portion to replace the first memory address with the second memory address.

Abstract: Enforcing shadow stack violations at module granularity, rather than at thread or process granularity. An exception is processed during execution of a thread based on code of an application binary, which is enabled for shadow stack enforcement, that calls an external module. The exception results from a mismatch between a return address popped from the thread's call stack and a return address popped from the thread's shadow stack. Processing the exception includes determining that the exception resulted from execution of an instruction in the external module, and determining whether or not the external module is enabled for shadow stack enforcement. Based at least on these determinations, execution of the thread is terminated when the external module is enabled for shadow stack enforcement, or the thread is permitted to continue executing when the external module is not enabled for shadow stack enforcement.

Abstract: A spinal implant device is provided comprising a body structure with a central cavity and a movable lid configured to cover the central cavity. The movable lid is configured to be opened to pack a material in the central cavity. The movable lid can be connected to the body structure with a moveable joint. The spinal implant device can include a compressible feature. A method for treating the spine is provided comprising opening a movable lid of a spinal implant device, packing a material in a central cavity of a spinal implant device, closing the movable lid, and inserting the spinal implant device between vertebrae.

Abstract: Enforcing shadow stack violations at module granularity, rather than at thread or process granularity. An exception is processed during execution of a thread based on code of an application binary, which is enabled for shadow stack enforcement, that calls an external module. The exception results from a mismatch between a return address popped from the thread's call stack and a return address popped from the thread's shadow stack. Processing the exception includes determining that the exception resulted from execution of an instruction in the external module, and determining whether or not the external module is enabled for shadow stack enforcement. Based at least on these determinations, execution of the thread is terminated when the external module is enabled for shadow stack enforcement, or the thread is permitted to continue executing when the external module is not enabled for shadow stack enforcement.

Abstract: Devices for fixing interbody fusion devices to bone by helically or corkscrew-shaped elements are provided. Methods for surgically implanting an interbody fusion device using helically-shaped fixation wire are provided.

Abstract: A spinal implant device is provided comprising a body structure with a central cavity and a movable lid configured to cover the central cavity. The movable lid is configured to be opened to pack a material in the central cavity. The movable lid can be connected to the body structure with a moveable joint. The spinal implant device can include a compressible feature. A method for treating the spine is provided comprising opening a movable lid of a spinal implant device, packing a material in a central cavity of a spinal implant device, closing the movable lid, and inserting the spinal implant device between vertebrae.

Abstract: A program is executed using a call stack and shadow stack. The call stack includes frames having respective return addresses. The frames may also store variables and/or parameters. The shadow stack stores duplicates of the return addresses in the call stack. The call stack and the shadow stack are maintained by, (i) each time a function is called, adding a corresponding stack frame to the call stack and adding a corresponding return address to the shadow stack, and (ii) each time a function is exited, removing a corresponding frame from the call stack and removing a corresponding return address from the shadow stack. A backtrace of the program's current call chain is generated by accessing the return addresses in the shadow stack. The outputted backtrace includes the return addresses from the shadow stack and/or information about the traced functions that is derived from the shadow stack's return addresses.

Abstract: Enforcing shadow stack violations at module granularity, rather than at thread or process granularity. An exception is processed during execution of a thread based on code of an application binary, which is enabled for shadow stack enforcement, that calls an external module. The exception results from a mismatch between a return address popped from the thread's call stack and a return address popped from the thread's shadow stack. Processing the exception includes determining that the exception resulted from execution of an instruction in the external module, and determining whether or not the external module is enabled for shadow stack enforcement. Based at least on these determinations, execution of the thread is terminated when the external module is enabled for shadow stack enforcement, or the thread is permitted to continue executing when the external module is not enabled for shadow stack enforcement.

Abstract: A spinal implant device is provided comprising a body structure with a central cavity and a movable lid configured to cover the central cavity. The movable lid is configured to be opened to pack a material in the central cavity. The movable lid can be connected to the body structure with a moveable joint. The spinal implant device can include a compressible feature. A method for treating the spine is provided comprising opening a movable lid of a spinal implant device, packing a material in a central cavity of a spinal implant device, closing the movable lid, and inserting the spinal implant device between vertebrae.

Abstract: Devices for fixing interbody fusion devices to bone by helically or corkscrew-shaped elements are provided. Methods for surgically implanting an interbody fusion device using helically-shaped fixation wire are provided.

Abstract: A program is executed using a call stack and shadow stack. The call stack includes frames having respective return addresses. The frames may also store variables and/or parameters. The shadow stack stores duplicates of the return addresses in the call stack. The call stack and the shadow stack are maintained by, (i) each time a function is called, adding a corresponding stack frame to the call stack and adding a corresponding return address to the shadow stack, and (ii) each time a function is exited, removing a corresponding frame from the call stack and removing a corresponding return address from the shadow stack. A backtrace of the program's current call chain is generated by accessing the return addresses in the shadow stack. The outputted backtrace includes the return addresses from the shadow stack and/or information about the traced functions that is derived from the shadow stack's return addresses.

Abstract: Enforcing shadow stack violations at module granularity, rather than at thread or process granularity. An exception is processed during execution of a thread based on code of an application binary, which is enabled for shadow stack enforcement, that calls an external module. The exception results from a mismatch between a return address popped from the thread's call stack and a return address popped from the thread's shadow stack. Processing the exception includes determining that the exception resulted from execution of an instruction in the external module, and determining whether or not the external module is enabled for shadow stack enforcement. Based at least on these determinations, execution of the thread is terminated when the external module is enabled for shadow stack enforcement, or the thread is permitted to continue executing when the external module is not enabled for shadow stack enforcement.