Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, while the IDE tool is compiling the source code of a development project, the IDE tool generates at least a first compiler warning. The first compiler warning generally corresponds to at least one line of source code in a first source code component of the development project. A first set of assertions to add to the source code of the development project is determined based on the line of source code that resulted in the first compiler warning. The IDE tool adds the first set of assertions to the source code of the development project. The first set of assertions are compiled as part of the source code of the development project.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, while the IDE tool is compiling the source code of a development project, the IDE tool generates at least a first compiler warning. The first compiler warning generally corresponds to at least one line of source code in a first source code component of the development project. A first set of assertions to add to the source code of the development project is determined based on the line of source code that resulted in the first compiler warning. The IDE tool adds the first set of assertions to the source code of the development project. The first set of assertions are compiled as part of the source code of the development project.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.

Abstract: The present disclosure relates to managing assertions in program source code in an integrated development environment (IDE) tool. According to one embodiment, the IDE tool receives a request to execute an application built from source code of a development project from a user interacting with an integrated development environment (IDE) tool. The IDE tool identifies changes to one or more of the source code of the development project from a previous version of the one or more source code. Based on the changes to the source code, the IDE tool selectively identifies one or more assertions to insert in the source code based on the identified changes.

Abstract: The present disclosure relates to maintaining assertions in source code components of a development project by an integrated development environment (IDE) tool. According to one embodiment, a request is received to build a software application generated from the development project. Based on prior executions of the software application, resource requirements for each of one or more assertions included in the prior executions of the software application are identified. One or more of the assertions based on the identified resource requirements are selectively inserted in the source code components. The source code components of the development project are compiled to build the software application.

Abstract: The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.

Abstract: The present disclosure relates to maintaining assertions in source code components of a development project by an integrated development environment (IDE) tool. According to one embodiment, a request is received to build a software application generated from the development project. Based on prior executions of the software application, resource requirements for each of one or more assertions included in the prior executions of the software application are identified. One or more of the assertions based on the identified resource requirements are selectively inserted in the source code components. The source code components of the development project are compiled to build the software application.

Abstract: The present disclosure relates to managing assertions in program source code in an integrated development environment (IDE) tool. According to one embodiment, the IDE tool receives a request to execute an application built from source code of a development project from a user interacting with an integrated development environment (IDE) tool. The IDE tool identifies changes to one or more of the source code of the development project from a previous version of the one or more source code. Based on the changes to the source code, the IDE tool selectively identifies one or more assertions to insert in the source code based on the identified changes.

Abstract: In an embodiment, a current internal corrosion level at a current time is read from an internal corrosion sensor that is internal to a computer. An internal corrosion difference is calculated between the current internal corrosion level and a previous internal corrosion level. Upon determining that the internal corrosion difference is more than a first threshold amount, a first action is performed that decreases an internal temperature of the computer. In a further embodiment, upon determining that the internal corrosion difference is less than a second threshold amount, a second action is performed that allows the internal temperature of the computer to increase.

Abstract: A method for controlling access to a memory of a computer system configured with at least one logical partition may include receiving a first request to map a first page of the memory, the request identifying a first requester. A first logical partition associated with the first page may be determined. It may be determined that an attribute of the first logical partition limits access to individual pages of the first logical partition to a single requester, and that the first page is available to be mapped to a requester. The first page may be mapped to the first requester and a flag indicating that the first page is unavailable for an additional mapping may be set. The first request may be from a device driver on behalf of an input/output adapter, as the first requester, to use the first page in a direct memory access transfer.

Abstract: An apparatus and method detect the use of stale data values due to weak consistency between parallel threads on a computer system. A consistency error detection mechanism uses object code injection to build a consistency error detection table during the operation of an application. When the application is paused, the consistency error detection mechanism uses the consistency error detection table to detect consistency errors where stale data is used by the application. The consistency error detection mechanism alerts the user/programmer to the consistency errors in the application program.

Abstract: A method for identifying code segments and associated software developers in a software development environment is disclosed. A software development tool detects a memory error in a first code segment. The software development tool associates the memory error with a first software developer that is associated with the first code segment. The software development tool identifies a second code segment related to the first code segment. The software development tool associates the memory error with a second software developer that is associated with the second code segment.

Abstract: A method for identifying code segments and associated software developers in a software development environment is disclosed. A software development tool detects a memory error in a first code segment. The software development tool associates the memory error with a first software developer that is associated with the first code segment. The software development tool identifies a second code segment related to the first code segment. The software development tool associates the memory error with a second software developer that is associated with the second code segment.

Abstract: Systems, methods, and computer program products to discover weak consistency errors in an application, by executing, by a debugger, a first thread of the application, by, determining that a first instruction in the first thread specifies to store a first value at a first memory address, setting a current value stored in the first memory address as an old value for the first memory address in a container for the first thread, executing the first instruction to store the first value at the first memory address, and setting the first value as a new value for the first memory address in the container for the first thread. The debugger then executes a second thread of the application, by restoring old values in the containers for all other threads and restoring a new value for each memory address specified in a container for the second thread to its respective memory address.

Abstract: Methods to discover weak consistency errors in an application, by executing, by a debugger, a first thread of the application, by, determining that a first instruction in the first thread specifies to store a first value at a first memory address, setting a current value stored in the first memory address as an old value for the first memory address in a container for the first thread, executing the first instruction to store the first value at the first memory address, and setting the first value as a new value for the first memory address in the container for the first thread. The debugger then executes a second thread of the application, by restoring old values in the containers for all other threads and restoring a new value for each memory address specified in a container for the second thread to its respective memory address.

Abstract: A mechanism is provided for enhancing a selection region for select information associated within a document. A document is analyzed to determine one or more pieces of information in the document that are likely to be selected by the user, wherein the one or more pieces of information are less than all of the information in the document. Responsive to the document failing to have been analyzed before, a selection region associated with each piece of information in the one or more pieces of information is enlarged by a first predetermined size amount thereby forming a respective region enlargement value for each piece of information in the one or more pieces of information. The region enlargement value for each piece of information in the one or more pieces of information is then recorded.

Abstract: In an embodiment, a current internal corrosion level at a current time is read from an internal corrosion sensor that is internal to a computer. An internal corrosion difference is calculated between the current internal corrosion level and a previous internal corrosion level. If the internal corrosion difference is more than a first threshold amount, a first action is performed that decreases an internal temperature of the computer.

Abstract: In an embodiment, an address watch is established on a memory address while the execution of a first thread of a program is halted. In response to a second thread modifying memory contents at the memory address, encountering the address watch and halting, a determination is made whether a first variable in the program that represents the memory address is displayed on a user interface for the first thread. If the first variable in the program that represents the memory address is displayed on the user interface for the first thread, the value of the first variable is read and displayed on the user interface of the first thread.

Abstract: A social media mechanism processes messages for content that may require filtering of recipients of the message, and informs a user who drafted the message when the message might need to be filtered so it is not sent to all potential recipients of the message. The user may then select to send the message to all potential recipients, or to filter the recipients so the message is sent to less than all of the potential recipients. User profiles are created and maintained, and may include information that helps to determine when filtering of messages is desirable. Feedback buttons are also provided to provide feedback when a user does not like a message.

Abstract: An apparatus and method detect the use of stale data values due to weak consistency between parallel threads on a computer system. A consistency error detection mechanism uses object code injection to build a consistency error detection table during the operation of an application. When the application is paused, the consistency error detection mechanism uses the consistency error detection table to detect consistency errors where stale data is used by the application. The consistency error detection mechanism alerts the user/programmer to the consistency errors in the application program.