DOCSLIB.ORG

Changelocator: Locate Crash-Inducing Changes Based on Crash Reports

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Changelocator: Locate Crash-Inducing Changes Based on Crash Reports Empir Software Eng https://doi.org/10.1007/s10664-017-9567-4 ChangeLocator: locate crash-inducing changes based on crash reports Rongxin Wu1 · Ming Wen1 · Shing-Chi Cheung1 · Hongyu Zhang2 © Springer Science+Business Media, LLC 2017 Abstract Software crashes are severe manifestations of software bugs. Debugging crashing bugs is tedious and time-consuming. Understanding software changes that induce a crashing bug can provide useful contextual information for bug fixing and is highly demanded by developers. Locating the bug inducing changes is also useful for automatic program repair, since it narrows down the root causes and reduces the search space of bug fix location. However, currently there are no systematic studies on locating the software changes to a source code repository that induce a crashing bug reflected by a bucket of crash reports. To tackle this problem, we first conducted an empirical study on characterizing the bug inducing changes for crashing bugs (denoted as crash-inducing changes). We also propose ChangeLocator, a method to automatically locate crash-inducing changes for a given bucket of crash reports. We base our approach on a learning model that uses features originated from our empirical study and train the model using the data from the historical fixed crashes. We evaluated ChangeLocator with six release versions of Netbeans project. The results show that it can locate the crash-inducing changes for 44.7%, 68.5%, and 74.5% of the Communicated by: Martin Monperrus and Westley Weimer Rongxin Wu [email protected] Ming Wen [email protected] Shing-Chi Cheung [email protected] Hongyu Zhang [email protected] 1 Department of Computer Science and Engineering, The Hong Kong University of Science and Technology, Hong Kong, China 2 School of Electrical Engineering and Computing, The University of Newcastle, Newcastle, Australia Empir Software Eng bugs by examining only top 1, 5 and 10 changes in the recommended list, respectively. It significantly outperforms the existing state-of-the-art approach. Keywords Crash-inducing change · Software crash · Crash stack · Bug localization 1 Introduction Software crashes are usually considered as severe bugs. They cause unintended program behaviour, bad user experiences, or even disasters for safe-critical systems. Various crash reporting systems such as Windows Error Reporting (Glerum et al. 2009), Apple Crash Reporter (Technical note tn2123: Crashreporter 2015), Mozilla Crash Reports (Mozilla crash reports 2015) and Netbeans Exception Reports (Netbeans exception reports 2015), have been developed and deployed. These systems (Technical note tn2123: Crashreporter 2015;Glerumetal.2009; Mozilla crash reports 2015; Netbeans exception reports 2015) automatically collect crash reports from end users and group similar crash reports into buckets, which are proved to be useful for prioritizing debugging effort (Glerum et al. 2009). However, automatic debugging for crashing bugs is not supported by existing crash reporting systems. Over the years, various bug localization techniques have been proposed to help develop- ers debug (e.g., Abreu et al. 2007:Jonesetal.2002; Liblit et al. 2003;Sahaetal.2013;Yeet al. 2014; Zhou et al. 2012; Wong et al. 2014). These techniques rank suspicious statements or modules based on execution traces or bug reports. Although these techniques could be useful in some situations, their effectiveness is largely unsatisfactory in practice and they are rarely used by developers (Parnin and Orso 2011). One reason is that locating buggy statements or modules in isolation may not provide adequate information for developers to understand the bugs (Parnin and Orso 2011). Our previous study (Wen et al. 2016) found that, in order to understand and fix a bug, developers often refer to the bug inducing changes (i.e., the commits that initially introduce the bug) in the discussion of bug reports. In our investigation, we found that 1,851 bug reports (Bug report list 2015) about crashes in Mozilla include developers’ discussion on bug inducing changes made to the repository. Developers extensively discussed “regression range” (i.e., the last known good revision to the first known bad revision) (Regression range 2015) in bug reports. We sampled some developers’ discussions and their desire to learn about bug inducing changes as follows. “given the regression range (for which I’m most grateful) ...1 Finding a regression range to find the change that busted it could be useful.2 Alternatively, you could check if you can reproduce on some of the older (archived) UX builds and/or otherwise get an idea of the regression range.3 And to be useful, the range (of course) needs to be narrow ... In my experience, given that narrow a regression range, it’s often possible to guess which patch triggered a 1https://bugzilla.mozilla.org/show bug.cgi?id=448608 2https://bugzilla.mozilla.org/show bug.cgi?id=589191 3https://bugzilla.mozilla.org/show bug.cgi?id=941044 Empir Software Eng problem. Then I could do a test build with that patch backed out, and ask you guys to test it.4 ... help in narrowing down the regression range and finding the right prod- uct/component is appreciated”.5 Based on our investigation of developers’ discussions and source code repository, we summarize four major benefits that developers can derive from understanding bug inducing changes. First, since a bug inducing change records the developer who committed it, it facilitates the triage of the bug to the developer who is familiar with the corresponding code. As shown in Fig. 1, the bug was fixed by the developer Vladimir Kvashin who was also the committer of the bug inducing changes. Our previous study (Wen et al. 2016) confirmed that 77.86% of the bugs were fixed by the committer of the bug inducing changes. Second, the modified code in the bug inducing changes provides the contextual clues that can help explain and fix the bugs. Take the bug #244574 as an example. This bug is an NullPointer Exception (Fig. 1a), and it crashes at Line 317 as shown in Fig. 1b. This crash is due to the null value of p.second(). From the bug inducing change, we can get the clue why p.second() is null. At Line 449, the return value is an object of Pair class whose field second is assigned with the null value. At Line 425, the object cur can be assigned with an object of Pair class which is returned from Line 449 (dotted line 1). The variable cur then can be assigned to another object result in the method getEnv at Line 428 (dotted line 2), and then result is returned (dotted line 3). At Line 315, the object p is assigned with the return value of the method getEnv and then used at Line 317 (dotted line 4). By examining the bug inducing code, we can understand how a null value is propagated to the variable used in crash point. Moreover, in Fig. 1c, the bug-fixing code at Line 317 and 319 is semantically equivalent to the deleted code before Line 315 in the bug inducing change, which indicates that developers can get hints of how to write the bug-fixing patch from the bug inducing change. Third, reverting bug inducing changes is one of the ways that developers resolve the bugs. In our investigation of NetBeans project, there are more than 1,069 bug inducing changes that were reverted for fixing bugs in the source code repository. Furthermore, the ability to locate the bug inducing changes is also beneficial for automatic program repair techniques (e.g., Le Goues et al. 2012; Arcuri and Yao 2008;Weimeret al. 2010 ), since it narrows down the root causes and reduces the search space of bug fix location. Although bug inducing changes are important to program debugging in practice, there are no systematic studies on how to locate these changes for the bugs discovered in the field. One relevant study is delta debugging (Zeller 1999), which intensively runs the test cases on the different combination of changes and locates the bug introducing changes. Similar to spectrum-based bug localization techniques, this technique assumes the availability of failing test cases, which is not generally valid for the bugs happened in the field. The other relevant studies (Kamei et al. 2013; Kim et al. 2008; An and Khomh 2015;Anetal.2017) are to predict whether a committed change is buggy. However, these techniques cannot distinguish which bug a buggy-prone change is blamed for, and developers may not know what to do without actionable information. 4https://bugzilla.mozilla.org/show bug.cgi?id=400291 5https://bugzilla.mozilla.org/show bug.cgi?id=446630 Empir Software Eng Bug: #244574 User:Exception Reporter Reported Date: May 18 18:16 2014 UTC Description: NullPointerException at org.netbeans.modules.cnd.makeproject.ui. RemoteSyncActions$BaseAction.enable (a) Bug #244574 changeset:e10374c2df360 user:Vladimir Kvashin date: Fri Feb 28 14:56:50 2014 summary: additional fix for #242416 Hide “upload to” action in the case remote host uses “System-level-file-sharing” - ExecutionEnvironment execEnv = getEnv(activatedNodes); - If (execEnv != null && execEnv.isRemote()) { - enabled = ServerList.get(execEnv).getSyncFactory().isCopying(); 315 + Pair p <ExecutionEnvironment, RemoteSyncFactory> = getEnv(activatedNodes); 316 + if(p != null4 && p.first()!= null&& p.first().isRemote()){ 317 + enabled = p.second().isCopying(); Crashing line 318 } else { 319 enabled = false; 320 } 3 421 + private static Pair<ExecutionEnvironment, RemoteSyncFactory> getEnv(Node[] activatedNodes) { 422 + Pair<ExecutionEnvironment, RemoteSyncFactory> result = null; 425 + Pair<ExecutionEnvironment, RemoteSyncFactory> curr = getEnv(project); 426 + if (curr!= null) { 427 if (result == null) { 2 - result = env; 428 + result = curr; 429 } 1 437 return result; 438 } 439 + private static Pair<ExecutionEnvironment,RemoteSyncFactory> getEnv(Project project) { 449 + return Pair.of(ServerList.getDefaultRecord().getExecutionEnvironment(),null); 450 } (b) Bug Inducing Change for Bug #244574 changeset:65f38533c2ea user:Vladimir Kvashin date: Tue May 20 17:42:33 2014 summary:fixed #244574–NullPointerExcetion at org.netbeans.
Load more

Recommended publications
  • Challenges and Issues of Mining Crash Reports
    Challenges and Issues of Mining Crash Reports Le An, Foutse Khomh SWAT, Polytechnique Montreal,´ Quebec,´ Canada fle.an, [email protected] Abstract—Automatic crash reporting tools built in many soft- In the rest of this paper, we describe the structure of a ware systems allow software practitioners to understand the crash report before presenting some analytic techniques to origin of field crashes and help them prioritise field crashes mine implicit information from crash reports. For each of the or bugs, locate erroneous files, and/or predict bugs and crash occurrences in subsequent versions of the software systems. In techniques, we discuss its challenges and issues. After giving this paper, after illustrating the structure of crash reports in an overview of the related work, we conclude the paper with Mozilla, we discuss some techniques for mining information from suggestions for future studies. crash reports, and highlight the challenges and issues of these techniques. Our aim is to raise the awareness of the research II. STRUCTURE OF CRASH REPORTS community about issues that may bias research results obtained In this section, we take crash reports from Mozilla Socorro from crash reports and provide some guidelines to address certain server (Mozilla’s crash collecting database) [4] as an example challenges related to mining crash reports. Index Terms—Crash report, bug report, mining software to describe the typical crash collecting system. repositories. Mozilla delivers its applications with a built-in automatic crash reporting tool: Mozilla Crash Reporter, which sends a crash report to the Mozilla Socorro server, once end users I. INTRODUCTION encounter an unexpected halt of the application.
    [Show full text]
  • Crash Reporting: Mozilla’S Open Source Solution
    Crash Reporting: Mozilla’s Open Source Solution K Lars Lohn Ted Mielczarek Austin King Friday, July 24, 2009 Howdy, I’m Lars from Mozilla, I’m here today with my colleagues, Ted Mill-char-ek and Austin King to talk about Crash Reporting. What is it? Friday, July 24, 2009 Have you ever seen Firefox crash? Have you ever wondered what happens after you hit the “restart firefox” button? In the next 45 minutes, we’re going to take you down the rabbit hole and show you what we do. We want our processes to be open. When you experience a problem with any Mozilla product, we want _everyone_, not just the developers, to watch the flow of information about a problem for its initial occurrence, through data collection and triage, on to Bugzilla and to an eventual resolution. Crash reporting is the transmission of information to the developers about the state of an application during a catastrophic failure. Friday, July 24, 2009 Crash reporting is the transmission of information about the state of an application during a catastrophic failure to the developers. The goal is to give the developers information that they would not otherwise have had. Google Socorro Socorro UI Breakpad Server (reporter) minidump_stackwalk Friday, July 24, 2009 Our crash reporting system can be divided into three parts. Breakpad - a google project - this code lives mainly within the Firefox application Socorro (in two movements) the backend server and the user interface running at Mozilla. written in three languages <click> <click> <click> Ted, Austin and I are the three developers in charge of the three sections.
    [Show full text]
  • An Autopsy of a Web Browser's Leaked Crash Reports
    Crashing Privacy: An Autopsy of a Web Browser’s Leaked Crash Reports Kiavash Satvat Nitesh Saxena University of Alabama at Birmingham University of Alabama at Birmingham [email protected] [email protected] ABSTRACT private information that can be found in crash reports which may Harm to the privacy of users through data leakage is not an un- pose a threat to the users’ privacy. known issue, however, it has not been studied in the context of In this paper, to demonstrate possible risks that the current the crash reporting system. Automatic Crash Reporting Systems implementation of ACRS may pose to users’ privacy, we study a (ACRS) are used by applications to report information about the er- dataset of partially anonymized crash reports released by one of 1 rors happening during a software failure. Although crash reports the major browsers . The current state of the art browsers collect are valuable to diagnose errors, they may contain users’ sensitive relatively similar data including browsed URL during the crash and information. In this paper, we study such a privacy leakage vis-a- runtime information, as they can be required for the debugging. vis browsers’ crash reporting systems. As a case study, we mine To the best of our knowledge, this is the first case study which a dataset consisting of crash reports collected over the period of scrutinizes a database of 2.5 million partially anonymized crash re- six years. Our analysis shows the presence of more than 20,000 ports, containing visited URLs, system runtime information and sessions and token IDs, 600 passwords, 9,000 email addresses, an users’ descriptions.
    [Show full text]
  • Why Did This Reviewed Code Crash? an Empirical Study of Mozilla Firefox
    Why Did This Reviewed Code Crash? An Empirical Study of Mozilla Firefox Le An and Foutse Khomh Shane McIntosh Marco Castelluccio Polytechnique Montréal McGill University Mozilla Corporation and Università Federico II {le.an, foutse.khomh}@polymtl.ca [email protected] [email protected] Abstract—Code review, i.e., the practice of having other team mine the crash collection, version control, issue tracking, and members critique changes to a software system, is a pillar of code reviewing systems of the Mozilla Firefox project. More modern software quality assurance approaches. Although this specifically, we address the following two research questions: activity aims at improving software quality, some high-impact defects, such as crash-related defects, can elude the inspection of RQ1: What are the characteristics of reviewed code that is reviewers and escape to the field, affecting user satisfaction and implicated in a crash? increasing maintenance overhead. In this research, we investigate We find that crash-prone reviewed patches often contain the characteristics of crash-prone code, observing that such code complex code, and classes with many other classes de- tends to have high complexity and depend on many other classes. In the code review process, developers often spend a long time on pending on them. Crash-prone patches tend to take a and have long discussions about crash-prone code. We manually longer time and generate longer discussion threads than classify a sample of reviewed crash-prone patches according to non-crash-prone patches. This result suggests that review- their purposes and root causes. We observe that most crash- ers need to focus their effort on the patches with high prone patches aim to improve performance, refactor code, add complexity and on the classes with a complex relationship functionality, or fix previous crashes.
    [Show full text]
  • City Research Online
    City Research Online City, University of London Institutional Repository Citation: Stankovic, V. and Strigini, L. (2009). A survey on online monitoring approaches of computer-based systems. London, UK: Centre for Software Reliability, City University London. This is the unspecified version of the paper. This version of the publication may differ from the final published version. Permanent repository link: https://openaccess.city.ac.uk/id/eprint/531/ Link to published version: Copyright: City Research Online aims to make research outputs of City, University of London available to a wider audience. Copyright and Moral Rights remain with the author(s) and/or copyright holders. URLs from City Research Online may be freely distributed and linked to. Reuse: Copies of full items can be used for personal research or study, educational, or not-for-profit purposes without prior permission or charge. Provided that the authors, title and full bibliographic details are credited, a hyperlink and/or URL is given for the original metadata page and the content is not changed in any way. City Research Online: http://openaccess.city.ac.uk/ [email protected] A survey on online monitoring approaches of computer-based systems Prepared by: Vladimir Stankovic, Lorenzo Strigini Date : June 2009 Version : 2.6 1/29 This report 1 surveys forms of online data collection that are in current use (as well as being the subject of research to adapt them to changing technology and demands), and can be used as inputs to assessment of dependability and resilience, although they are not primarily meant for this use. 1. Introduction Monitoring the components of a system can be used to make decisions about the management of the system and thus control its behaviour.
    [Show full text]
  • The Unreasonable Effectiveness of Traditional Information Retrieval in Crash Report Deduplication
    The Unreasonable Effectiveness of Traditional Information Retrieval in Crash Report Deduplication Joshua Charles Eddie Antonio Santos Abram Hindle Campbell Department of Computing Department of Computing Department of Computing Science Science Science University of Alberta University of Alberta University of Alberta Edmonton, Canada Edmonton, Canada Edmonton, Canada [email protected] [email protected] [email protected] ABSTRACT Organizations like Mozilla, Microsoft, and Apple are flooded Ada is a senior software engineer at Lovelace Inc., a large with thousands of automated crash reports per day. Al- software development company. Lovelace has just shipped though crash reports contain valuable information for de- the latest version of their software to hundreds of thousands bugging, there are often too many for developers to examine of users. A short while later, as Ada is transitioning her team individually. Therefore, in industry, crash reports are often to other projects, she gets a call from the quality-assurance automatically grouped together in buckets. Ubuntu’s repos- team (QA) saying that the software she just shipped has itory contains crashes from hundreds of software systems a crashing bug affecting two-thirds of all users. Worse yet, available with Ubuntu. A variety of crash report bucket- Ada and her team can’t replicate the crash. What would ing methods are evaluated using data collected by Ubuntu’s really be helpful is if every time that crash was encountered Apport automated crash reporting system. The trade-off be- by a user, Lovelace would automatically receive a crash re- tween precision and recall of numerous scalable crash dedu- port [1], with some context information about what machine plication techniques is explored.
    [Show full text]
  • Supporting Software Development Based on Crash Report Mining and Analysis
    CrashAwareDev: Supporting Software Development based on Crash Report Mining and Analysis Leandro Beserra*y, Roberta Coelhoy *Informatics Superintendence yDepartment of Informatics and Applied Mathematics Federal University of Rio Grande do Norte Natal, Brazil [email protected], [email protected] Abstract— Exception handling mechanisms are a com- of a program [2], allowing exceptions to be th- mon feature of mainstream programming languages to rown, captured, and handled at different points deal with exceptional conditions. If on the one hand in the system. However, the exception handling they allow the programmer to prepare the code to deal code designed to make a system more robust often with exceptional conditions, on the other hand they can become a source of bugs that threatens the application works the other way around and become a burden robustness – studies have shown that uncaught exceptions programmers has to cope with, leading to bugs are the main cause of application crashes. To keep track such as the uncaught exceptions. The uncaught of crashes and enable an easier fault localization, several exceptions are the main cause of crashes in Java applications, nowadays, use crash reporting tools. In software systems [3]. A crash is an abnormal this work, we propose a tool named CrashAwareDev, behavior of a system that leads to the interruption integrated with the Eclipse IDE, which mines the in- formation available in crash reporting tools to support of its execution. programmers in their day-to-day activities. The proposed After a crash occurs, systems typically store tool alerts developers about the classes related to recent information related to the crash on crash report crashes and warns about source code characteristics (bug systems.
    [Show full text]
  • Privacy-Aware Remote Error Analysis on Commodity Software
    Panalyst: Privacy-Aware Remote Error Analysis on Commodity Software Rui Wang†, XiaoFeng Wang† and Zhuowei Li‡ †Indiana University at Bloomington, ‡Center for Software Excellence, Microsoft wang63,xw7 @indiana.edu, [email protected] { } Abstract typically achieved by running an error reporting tool on a client system, which gathers data related to an applica- Remote error analysis aims at timely detection and rem- tion’s runtime exception (such as a crash) and transmits edy of software vulnerabilities through analyzing run- them to a server for diagnosis of the underlying software time errors that occur on the client. This objective can flaws. This paradigm has been widely adopted by soft- only be achieved by offering users effective protection ware manufacturers. For example, Microsoft relies on of their private information and minimizing the perfor- WER to collect data should a crash happen to an applica- mance impact of the analysis on their systems without tion. Similar tools developed by the third party are also undermining the amount of information the server can extensively used. An example is BugToaster [27], a free access for understanding errors. To this end, we propose crash analysis tool that queries a central database using in the paper a new technique for privacy-aware remote the attributes extracted from a crash to seek a potential analysis, called Panalyst. Panalyst includes a client com- fix. These tools, once complemented by automatic anal- ponent and a server component. Once a runtime excep- ysis mechanisms [44, 34] on the server side, will also tion happens to an application, Panalyst client sends the contribute to quick detection and remedy of critical se- server an initial error report that includes only public in- curity flaws that can be exploited to launch a large-scale formation regarding the error, such as the length of the cyber attack such as Worm epidemic [47, 30].
    [Show full text]
  • Statistical Debugging
    Statistical Debugging Ben Liblit, University of Wisconsin–Madison What’s This All About? ` Statistical Debugging & Cooperative Bug Isolation ` Observe deployed software in the hands of real end users ` Build statistical models of success & failure ` Guide programmers to the root causes of bugs ` Make software suck less ` Lecture plan 1. Motivation for post-deployment debugging 2. Instrumentation and feedback 3. Statistical modeling and (some) program analysis 4. Crazy hacks, cool tricks, & practical considerations Credit Where Credit is Due ` Alex Aiken ` Akash Lal ` David Andrzejewski ` Junghee Lim ` Piramanayagam ` Mayur Naik Arumuga Nainar ` Jake Rosin ` Ting Chen ` Umair Saeed ` Greg Cooksey ` Alice Zheng ` Evan Driscoll ` Xiaojin Zhu ` Jason Fletchall ` … and an anonymous ` Michael Jordan cast of thousands! ` Anne Mulhern ` Or maybe just hundreds? ` Garrett Kolpin ` I don’t really know Motivations: Software Quality in the Real World “There are no significant bugs in our released software that any significant number of users want fixed.” Bill Gates, quoted in FOCUS Magazine A Caricature of Software Development Requirements Architecture & Design Implementation Testing & Verification Maintenance A Caricature of Software Development Requirements Architecture & Design Implementation Testing & Verification Maintenance Software Releases in the Real World [Disclaimer: this may also be a caricature.] Software Releases in the Real World 1. Coders & testers in tight feedback loop ` Detailed monitoring, high repeatability ` Testing approximates
    [Show full text]
  • A Crash Reporting Library for Android
    Masaryk University Faculty of Informatics A Crash Reporting Library for Android Master’s Thesis Marek Osvald Brno, Autumn 2017 Masaryk University Faculty of Informatics A Crash Reporting Library for Android Master’s Thesis Marek Osvald Brno, Autumn 2017 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Marek Osvald Advisor: prof. RNDr. Václav Matyáš M.Sc. Ph.D. i Acknowledgement This work was carried out during the years 2016-2017 at AVG Technolo- gies CZ and the Faculty of Informatics at the Masaryk University in Brno. It is a pleasure to use this page to sincerely thank all the people contributing or otherwise involved in the development of this thesis. I owe my deepest gratitude to my thesis supervisor, professor Václav Matyáš. His continuous support helped me to write a thesis worthy of a prestigious institution such as the Masaryk University. I am deeply grateful to my technical supervisor Petr Koudelka for his continuous optimism and guidance during the development. His advise helped me on countless occasions. I would like to express my most sincere gratitude to Philip M. Gammon who answered my English-related questions and selflessly offered proofreading this text. I am particularly grateful for support given by Katarína Varačková and Petr Buno during the initial prototype development.
    [Show full text]
  • Stephen a Ridley
    Escaping The Sandbox (Summer 2010) SyScan-EuSecWest-ReCon Stephen A. Ridley Senior Researcher Matasano Security [email protected] @s7ephen (Twitter) Thursday, July 15, 2010 Who I am. Stephen A. Ridley Senior Security Researcher (Matasano) • Previously: Senior Security Architect at McAfee, founding member of Security Architecture Group • Prior to that: Researcher at leading Defense contractor. Directly supported U.S. Defense and Intelligence communities in realm of software exploitation and software reverse engineering • Columnist for/interviewed by IT magazines (Wired, Ping!, Washington Post) • Kenshoto DefCon CTF organizers for a few years • blog: http://www.dontstuffbeansupyournose.com • Guest Lecturer/Instructor (New York University, Netherlands Forensics Institute, Department of Defense, Google, et al) • My Focus: software reverse engineering, software development, software exploitation, software security, Kernels (Microsoft ones for now). Increasingly interested in embedded systems and mobile devices Thursday, July 15, 2010 What am I talkin’ ‘bout today? ★ Sandboxing Overview (very brief ;-) • Goals, Sandbox Architecture (Chrome) ★ Sandboxes from a User-space Perspective • Securable Objects and SID apertures • Patches/Hooks/Interception • user32 issues ★ Sandboxes from a Kernel-space Perspective • Between User-space and Kernel-space • Kernel supported “Quasi Securable Objects”, Native API • Job Objects handle the rest, or do they? ★ Tools/Techniques/Demos • SandKit Toolkit (code injection, copymem, memdiff, hookfix, sa7shell, bincompare, dumptoken, tokenbrute, handlebrute) • Using Sandbox PoC Project (from Google) • Using kernel debugger while attacking Chrome • Triggering Chrome Bugs and where to start Thursday, July 15, 2010 Presentation Focus ★ Sandbox implementations are (by their nature) strongly coupled to the Operating System ★ This presentation focuses on Microsoft Windows Operating Systems and the NT Kernel (XP and Vista) • Side Note: Check out OSX’s DAC/Sandbox.
    [Show full text]
  • Look 360: an Android Application Using Google Analytics and Firebase with Mobile Cloud Computing
    International Journal of Scientific & Engineering Research Volume 12, Issue 3, March-2021 ISSN 2229-5518 50 Look 360: An android application using Google analytics and firebase with Mobile Cloud Computing. Rawat Deepak Umesh Prathamesh Sonawane Swapnil H Patil UG Student,PHCASC,Rasayani UG Student,PHCASC,Rasayani Asst.Professor ,PHCASC,Rasayani [email protected] [email protected] [email protected] 8355974361 8308380232 9699900007 Abstract— Look 360 is an Android Mobile Application; the name “Look360” originates by keeping its features in mind and considering its capabilities of storing Events, Seminars, Trade Shows and Conferences all across India on the Basis of different categories which has high search index as well as interest of the Students and Educators. Since, Look 360 handles the storing Events, Seminars, Trade Shows and Conferences Nationwide; filtration plays an important role here. This Android Application is connected with Google Firebase which uses Real Time Database feature. Using Real-Time Database enables the system to make changes with respect to Names of events, Date and Time and Venue of events too as specified by the Organizing Team. In order to make a Fully Dynamic Native Android Application the static contents need to be connected with the Cloud, thus Firebase Remote Config comes in picture to make Text, Colour etc feel dynamic. Look 360 is integrated with Google Action which can be evoked by just saying, “Ok Google, Talk to Look 360” where users can Operates the Application based on Voice Command. Google Action used Artificial Intelligence to get output based on Human Interactions via Keyboard or Voice. This Dynamic Android Application not only have Interesting User Interface (UI) but also it built by keeping User Experience (UX) among top priorities.
    [Show full text]