System and method for data collection and analysis of information relating to mobile applications

• US 9,606,904 B1
• Filed: 09/03/2014
• Issued: 03/28/2017
• Est. Priority Date: 12/12/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Crashlytics Inc. (Alphabet Inc.)
• Inventors: Chang, Wayne, Seibert, Jeffrey H. Jr.
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): Kabir, Mohammad
• Application Number:
  US14/476,103
• Time in Patent Office: 937 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0742 in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: G06F 11/0784 Routing of error reports, e.g. with a specific transmission path or data flow
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

A system and method are provided for data collection and analysis of information related to applications. Specifically, the developer of the application may install analytic software, which may be embodied as a software development kit (SDK), on an integrated development environment (“IDE”) associated with the developer, wherein the analytic software may be installed with a wizard-like interface having a series of easy to follow instructions. Once installed, the application, with the analytic software incorporated therein, may be provided and installed on a plurality of end user devices. Thereafter, the analytic software may work in conjunction with analytic processing logic to assist the developer in obtaining pertinent information related to bugs associated with the application that is being executed on an end user device.

Claims

1. A method for analyzing information relating to mobile applications, comprising:

performing, by a computer processor, a first launch of an application installed on an end user device, the first launch occurring at a first time and the application occupying a first memory address space on the end user device after the first launch;

incurring, by the application installed on the end user device, a bug resulting in production of crash data;

performing, by the computer processor, a second launch of the application on the end user device, the second launch occurring at a second time that is after the first time and the application occupying a second memory address space on the end user device after the second launch, wherein the first memory address space and the second memory address space are different;

determining a slide between the first launch and the second launch of the application based at least on the first memory address space and the second memory address space, wherein the slide is an offset between starting addresses and ending addresses of the first memory address space and the second memory address space; and

processing the crash data utilizing the slide to identify information associated with the bug.

2. The method of claim 1 wherein the end user device is one selected from a group consisting of a mobile phone, a personal digital assistant (PDA), and a personal computer (PC).

3. The method of claim 1, further comprising:

recording memory addresses for instructions pointers associated with the first launch of the application in response to incurring the bug, wherein the memory addresses are within the first memory address space.

4. The method of claim 1, wherein processing the crash data further comprises:

identifying an instruction pointer associated with the first launch of the application that incurred the bug, the instruction pointer having a particular memory address within the first memory address space;

determining a library, associated with the application, that has a first starting memory address and a first ending memory address that surround the instruction pointer;

subtracting the first starting memory address of the library from the particular memory address of the instruction pointer to obtain a de-based instruction pointer address, the first starting memory address of the library associated with the first launch of the application;

adding a second starting memory address of the of the library to the de-based instruction pointer address to obtain a re-based instruction pointer address, the second starting memory address of the library associated with the second launch of the application; and

determining a difference between the particular memory address of the instruction pointer and the re-based instruction pointer to obtain the slide.

5. The method of claim 1, further comprising:

executing, by the computer processor, an operating system that utilizes Address-Space Layout Randomization (ASLR) to store the application in the first memory address space after the first launch; and

executing, by the computer processor, the operating system that utilizes the ASLR to store the application in the second memory address space after the second launch.

6. The method of claim 1, further comprising:

receiving one or more input commands on the end user device indicating whether the crash reporting is enabled or disabled;

in response to determining that crash reporting is enabled, transmitting the crash data to an external server over a computer network; and

in response to determining that crash reporting is disabled, maintaining the crash data on the end user device without sending the crash data to the external server.

7. The method of claim 1, further comprising:

reporting the information associated with the bug to an external server.

8. A non-transitory computer-readable storage medium comprising a plurality of instructions configured to execute on at least one computer processor to enable the computer processor to:

perform a first launch of an application installed on an end user device, the first launch occurring at a first time and the application occupying a first memory address space on the end user device after the first launch;

identify that the application installed on the end user device incurred a bug resulting in production of crash data;

perform a second launch of the application on the end user device, the second launch occurring at a second time that is after the first time and the application occupying a second memory address space on the end user device after the second launch, wherein the first memory address space and the second memory address space are different; and

determine a slide between the first launch and the second launch of the application based at least on the first memory address space and the second memory address space, wherein the slide is an offset between starting addresses and ending addresses of the first memory address space and the second memory address space, wherein the slide is utilized to process the crash data to identify information associated with the bug.

9. The non-transitory computer-readable storage medium of claim 8 wherein the end user device is one selected from a group consisting of a mobile phone, a personal digital assistant (PDA), and a personal computer (PC).

10. The non-transitory computer-readable storage medium of claim 8, the plurality of instructions further configured to enable the computer processor to:

record memory addresses for instructions pointers associated with the first launch of the application in response to incurring the bug, wherein the memory addresses are within the first memory address space.

11. The non-transitory computer-readable storage medium of claim 8, the plurality of instructions further configured to enable the computer processor to:

identify an instruction pointer associated with the first launch of the application that incurred the bug, the instruction pointer having a particular memory address within the first memory address space;

determine a library, associated with the application, that has a first starting memory address and a first ending memory address that surround the instruction pointer;

subtract the first starting memory address of the library from the particular memory address of the instruction pointer to obtain a de-based instruction pointer address, the first starting memory address of the library associated with the first launch of the application;

add a second starting memory address of the of the library to the de-based instruction pointer address to obtain a re-based instruction pointer address, the second starting memory address of the library associated with the second launch of the application; and

determine a difference between the particular memory address of the instruction pointer and the re-based instruction pointer to obtain the slide.

12. The non-transitory computer-readable storage medium of claim 8, the plurality of instructions further configured to enable the computer processor to:

execute an operating system that utilizes Address-Space Layout Randomization (ASLR) to store the application in the first memory address space after the first launch; and

execute the operating system that utilizes the ASLR to store the application in the second memory address space after the second launch.

13. The non-transitory computer-readable storage medium of claim 8, the plurality of instructions further configured to enable the computer processor to:

receive one or more input commands on the end user device indicating whether the crash reporting is enabled or disabled;

transmit the crash data to an external server over a computer network when crash reporting is enabled; and

maintain the crash data on the end user device without sending the crash data to the external server when crash reporting is disabled.

14. The non-transitory computer-readable storage medium of claim 8, the plurality of instructions further configured to enable the computer processor to:

report the information associated with the bug to an external server.

15. A system comprising:

an end user device having a first processor and a first memory, the end user device configured to;

perform a first launch of an application installed on the end user device, the first launch occurring at a first time and the application occupying a first memory address space on the end user device after the first launch,

identify that the application installed on the end user device incurred a bug resulting in production of crash data,

perform a second launch of the application on the end user device, the second launch occurring at a second time that is after the first time and the application occupying a second memory address space on the end user device after the second launch, wherein the first memory address space and the second memory address space are different, and

determine a slide between the first launch and the second launch of the application based at least on the first memory address space and the second memory address space, wherein the slide is an offset between starting addresses and ending addresses of the first memory address space and the second memory address space; and

a developer device having a second processor and a second memory, the developer device configured to;

process the crash data utilizing the slide to identify information associated with the bug.

16. The system of claim 15 wherein the end user device is one selected from a group consisting of a mobile phone, a personal digital assistant (PDA), and a personal computer (PC).

17. The system of claim 15, wherein the end user device is further configured to:

record memory addresses for instructions pointers associated with the first launch of the application in response to incurring the bug, wherein the memory addresses are within the first memory address space.

18. The system of claim 15, wherein the end user device is further configured to:

identify an instruction pointer associated with the first launch of the application that incurred the bug, the instruction pointer having a particular memory address within the first memory address space,

determine a library, associated with the application, that has a first starting memory address and a first ending memory address that surround the instruction pointer;

subtract the first starting memory address of the library from the particular memory address of the instruction pointer to obtain a de-based instruction pointer address, the first starting memory address of the library associated with the first launch of the application,

add a second starting memory address of the of the library to the de-based instruction pointer address to obtain a re-based instruction pointer address, the second starting memory address of the library associated with the second launch of the application, and

determine a difference between the particular memory address of the instruction pointer and the re-based instruction pointer to obtain the slide.

19. The system of claim 15, wherein the end user device is further configured to:

execute an operating system that utilizes Address-Space Layout Randomization (ASLR) to store the application in the first memory address space after the first launch, and

execute the operating system that utilizes the ASLR to store the application in the second memory address space after the second launch.

20. The system of claim 15, wherein the end user device is further configured to:

receive one or more input commands on the end user device indicating whether the crash reporting is enabled or disabled,

transmit the crash data to an external server over a computer network when crash reporting is enabled, and

maintain the crash data on the end user device without sending the crash data to the external server when crash reporting is disabled.