Localizing the Buggy Method Sample Clauses

Localizing the Buggy Method. The method that manifests an error is not necessarily buggy. Rather, it is often one of its callees (or a callee of a callee) that is buggy. For example, one bug report of Joda-Time (bug 2025928) reports that method print does not behave as expected (i.e., nothing is output when “0” should be output). However, in fact, it turns out that print itself is not buggy. Instead, another method getFieldValue is found to be buggy; print eventually calls getFieldValue before it returns, and the wrong return value of getFieldValue propagates to print, where an error is manifested. In such a case where the method that manifests an error (e.g., print) is not buggy itself, one first needs to localize the buggy method (e.g., getFieldValue). We found that our checker can help localize the buggy method. We first started with writing a change contract of print, reflecting our intention to fix the manifested error. Our initial trial of verification failed. By looking at the generated counterexample, we were able to find that one of the callees (i.e., printTo) should change its behavior to satisfy the given change contract. Once we assigned a proper change contract to this callee, CCC succeeded. That is, the change contract of print was successfully verified, assuming that the change contract of printTo is correct. To see whether the assumption we made is true, we tried to verify printTo. Again, our initial verification trial failed, and we repeated looking for suspicious method calls in a counterexample to assign proper change contracts to them. We repeated this procedure until we reached the buggy getFieldValue method whose change contract was successfully verified, without having to assign change contracts to callees. The L section of the table shows the experimental data obtained through this repeated procedure, with the top row corresponding to print (where an error is manifested), the next row to a callee of print, and so on, and finally at the bottom row to getFieldValue, the buggy method.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Localizing the Buggy Method

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

  • AT&T-12STATE acknowledges that CLEC may have an embedded base of one-way trunks ordered and installed prior to the Effective Date of this Agreement that were used for termination of CLEC’s Section 251(b)(5)/IntraLATA Toll Traffic to AT&T-12STATE (Embedded Base). To the extent that CLEC has such an Embedded Base, CLEC shall only augment trunk groups in the Embedded Base with the mutual agreement of the Parties. CLEC shall not order any new one-way trunk groups following the Effective Date of this Agreement. Moreover, the Parties agree that the Embedded Base will be converted to two-way trunk groups under the following circumstances:

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers.

  • Other Methods of Procurement of Consultants’ Services The following table specifies methods of procurement, other than Quality and Cost-based Selection, which may be used for consultants’ services. The Procurement Plan shall specify the circumstances under which such methods may be used. Procurement Method

  • REQUIRED CONTENT FOR ARTICULATION 1. Career Assessments

  • Particular Methods of Procurement of Consultants’ Services 1. Quality- and Cost-based Selection. Except as otherwise provided in paragraph 2 below, consultants’ services shall be procured under contracts awarded on the basis of Quality and Cost-based Selection.

  • Linking to the Website and Social Media Features You may link to our homepage, provided you do so in a way that is fair and legal and does not damage our reputation or take advantage of it, but you must not establish a link in such a way as to suggest any form of association, approval, or endorsement on our part. This Website may provide certain social media features that enable you to: • Link from your own or certain third-party websites to certain content on this Website. • Send emails or other communications with certain content, or links to certain content, on this Website. • Cause limited portions of content on this Website to be displayed or appear to be displayed on your own or certain third-party websites. You may use these features solely as they are provided by us, and solely with respect to the content they are displayed with, and otherwise in accordance with any additional terms and conditions we provide with respect to such features. Subject to the foregoing, you must not: • Establish a link from any website that is not owned by you. • Cause the Website or portions of it to be displayed on, or appear to be displayed by, any other site, for example, framing, deep linking, or in-line linking. • Link to any part of the Website other than the homepage. • Otherwise take any action with respect to the materials on this Website that is inconsistent with any other provision of these Terms of Use. The website from which you are linking, or on which you make certain content available, must comply in all respects with the Content Standards set out in these Terms of Use. You agree to cooperate with us in causing any unauthorized framing or linking immediately to stop. We reserve the right to withdraw linking permission without notice. We may disable all or any social media features and any links at any time without notice in our discretion.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Portion of Products/Services Available If only a portion of Products and/or Services is available for shipment or performance to meet the Delivery Date, Supplier shall promptly notify DXC and proceed unless otherwise directed by DXC. Supplier shall be responsible for any cost increase in the shipment of Products due to its failure to meet the Delivery Date and/or if such method does not comply with DXC’s shipping instructions.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

Time is Money Join Law Insider Premium to draft better contracts faster.