<?xml version="1.0" encoding="UTF-8"?><ns2:project xmlns:ns1="http://gtr.rcuk.ac.uk/gtr/api" xmlns:ns2="http://gtr.rcuk.ac.uk/gtr/api/project" xmlns:ns3="http://gtr.rcuk.ac.uk/gtr/api/fund" xmlns:ns4="http://gtr.rcuk.ac.uk/gtr/api/person" xmlns:ns5="http://gtr.rcuk.ac.uk/gtr/api/project/outcome" xmlns:ns6="http://gtr.rcuk.ac.uk/gtr/api/organisation" ns1:created="2026-06-03T15:52:43Z" ns1:href="http://gtr.ukri.org/gtr/api/projects/F39975A1-BCEE-419B-B63A-7216CCC86EEC" ns1:id="F39975A1-BCEE-419B-B63A-7216CCC86EEC"><ns1:links><ns1:link ns1:href="http://gtr.ukri.org/gtr/api/persons/3D1EA1E9-F726-43F9-BA99-9BEBDB5A4945" ns1:rel="PM_PER"/><ns1:link ns1:href="http://gtr.ukri.org/gtr/api/organisations/516D5365-953D-4C63-85B5-011FC7A5B6FD" ns1:rel="LEAD_ORG"/><ns1:link ns1:href="http://gtr.ukri.org/gtr/api/organisations/516D5365-953D-4C63-85B5-011FC7A5B6FD" ns1:rel="PARTICIPANT_ORG"/><ns1:link ns1:end="2015-03-30T23:00:00Z" ns1:href="http://gtr.ukri.org/gtr/api/funds/F1AB8C51-5DD0-4E9C-8095-5F219FF98F1A" ns1:rel="FUND" ns1:start="2014-03-01T00:00:00Z"/></ns1:links><ns2:identifiers><ns2:identifier ns2:type="RCUK">710444</ns2:identifier></ns2:identifiers><ns2:title>The Undo Flight Recorder: a new approach to fixing software failures in the field</ns2:title><ns2:status>Closed</ns2:status><ns2:grantCategory>GRD Proof of Concept</ns2:grantCategory><ns2:leadFunder>Innovate UK</ns2:leadFunder><ns2:abstractText>this is a proposal for the development of a new technology to assist in the diagnosis and
fixing of Linux software failures (i.e. bugs): the Undo Flight Recorder (UFR). Software is
written by developers working for a Software Vendor, and consumed by an End User. End
users may also work for the software vendor (e.g. in-house developers, testing departments),
although more usually for another organisation. When software contains bugs, the end user
will suffer crashes and/or a decrease in their applications’ performance. Buggy software
creates significant costs to the vendor and represents even greater costs to the end user. It is
the software vendor’s responsibility to fix bugs reported by end users.
To analyse an end user reported software failure, developers must (1) reproduce in-house, or
(2) gain remote access to the end user’s computer, or (3) travel to the end user’s site, or (4)
use an error-reporting scheme to gather sufficient information. Error-reporting schemes are
desirable as 1-3 are usually expensive and time-consuming and often impossible. However,
existing error-reporting schemes tend to contain at best a snapshot of the program state at the
time of the failure, with very limited information about what led up to the failure. UFR is an
error-reporting scheme significantly better than anything currently in use. It removes the need
to reproduce software failures. Once embedded into the software vendor’s program, UFR
enables the program to record itself. The resulting recording contains everything the buggy
program did and can be loaded into the developer’s computer for analysis. Furthermore, the
Linux debugging tools market is under-developed when compared to tools available for other
operating systems such as Windows.</ns2:abstractText></ns2:project>