Need a way to stop running programs

Since the upgrade to os4, I have had to restart my phone almost daily. It seems that when I start an app, it continues to run even after I close it which is great for some apps but others I would rather stop running them when I close them. Is there an app for that?
Message was edited by: mitch236 to change the os

http://whenwillapple.com/blog/2010/04/19/iphone-os-4-multitasking-explained-agai n/

Similar Messages

How do I stop running programs.

I am using my Imac for recording purpose so I would like to stop the programs which are not needed.that may be running in the background.On my pc I go to the tak manager & find what is running.Is there a task manager type thing where I can go & stop running programs that use up CPU & cuase clicks & noises during recording.

You can use the Activity Monitor located at the Applications/Utilities. You can also access this by simultaneous pressing on your keyboard the following keys: Command Option and Esc. That would prompt you to a window called Force Quit. There you would see applications that are running.
Another option is like what is stated above, that you can see in your Dock what applications are running. You would see a little blue shining circle/oval below the open applications. Just left click for 1-2 sec the icon of the program you want to close and click on Quit.
Hope this would help you and good luck with your recording!

Is there any way to stop running apps from showing in dock

Is there any way to stop running applications from showing in the dock

MacUpdate.com for OnyX or TinkerTool, one of those has the ability to lock the Dock so no changes occur, basically giving you what you want.

Ios 7.0.2 issue: how to stop running programs

I am a new iPhone5 user and just installed ios 7.0.2 (maybe I should not have but I did). Now I don't know how to stop running programs. Previously
I double-clicked the Home button, then saw the icons that represented running programs, then could lightly touch one of them which led to all of them
showing a X for a potential delete. That does not work now so how do I do it?

Double click the home button and then swipe up on the app screenshots.

Need a way to safely exit program

We need a way to detect if a user close or ends our cvi application prematurely.
I can detect if someone kill the application using task manager. However if my function completes the program does not end..
How do I get my program to continue once the thread is complete? The below code shows how I am trying to test this.
#include <ansi_c.h>
#include <utility.h>
#include <userint.h>
int CVICALLBACK EventFunctionName (int panelOrMenuBarHandle, int controlOrMenuItemID, int event, void *callbackData, int eventData1, int eventData2)
if (event==EVENT_END_TASK)
if (ConfirmPopup ("Shut Down Detected", "Power to module turned off")!=1)
return -1;
return 0;
int CVICALLBACK InfinateLoop(void *functionData)
int count = 0;
while (1){
printf("Count is: %d\n", count);
Delay(1.0);
count++;
if(count == 5){
return 1;
return 0;
int main(int argc, char *argv[]){
int functionId;
InstallMainCallback (EventFunctionName, 0, 0); //EVENT_END_TASK
CmtScheduleThreadPoolFunction (DEFAULT_THREAD_POOL_HANDLE, InfinateLoop, NULL, &functionId);
RunUserInterface ();

Hey Malcrow,
I'm not exactly sure what you are trying to do.
Are you trying to allow your program to complete once the user tries to end it? Or are you just trying to detect that a user is closing the program?
If you want the program to finish, you may need to look into swallowing the event.
Here are some links that may help:
Using Callback Functions to Respond to User Interface Events
EVENT_END_TASK
Swallowing Events
Regards,
Jake G.
National Instruments
Applications Engineer

Apple script stops running program

Im am working on a project in apple script where basically you can talk to the computer in a way by pressing buttons for your response. But that is no the important part.... Whenever I try to run it it stops running at a certain point. Why is this?

At what point does it stop running?

Stop Running Programs with Java

Does anyone know how to stop a non-Java program that is currently running on a PC?

Hi,
did you started the programm from your java app with proc = Runtime.getRuntime.exec()?
If yes, you can kill it with
proc.destroy()If not, there is no platform-independent way to do it.
Best regards,
Martin

Need a way to inventory Mac programs and corresponding serial numbers

My boss is a Windows guy & doesn't know what he's doing. Therefore, he insists there's a way out there to inventory all of our office's Macs & generate a list of programs and corresponding serial #s. Is this possible? How?
In his perfect Microsoft world, this would create an Excel sheet.

If you've purchased and configured Apple Remote Desktop, then use the Application Usage Report feature -- gives a list of apps and how frequently they are used (in case you want to reigh in licenses).
A cheap alternative, of course, is to create an admin account on each machine and use 'ssh' to run system_profiler on each machine. e.g. 'system_profiler -detailLevel full SPApplicationsDataType'. You get responses like this (you can request an XML format too):
    Microsoft Word:
      Version: 14.1.2
      Last Modified: 6/15/11 10:05 AM
      Kind: Intel
      64-Bit (Intel): No
      Get Info String: 14.1.2 (110505), © 2010 Microsoft Corporation. All rights reserved.
      Location: /Applications/Microsoft Office 2011/Microsoft Word.app
    TextEdit:
      Version: 1.6
      Last Modified: 6/29/09 9:00 PM
      Kind: Intel
      64-Bit (Intel): Yes
      Location: /Applications/TextEdit.app
    Network Utility:
      Version: 1.4.6
      Last Modified: 6/25/09 5:20 PM
      Kind: Intel
      64-Bit (Intel): Yes
      Get Info String: Version 1.4.6, Copyright © 2000-2009 Apple Inc. All rights reserved.
      Location: /Applications/Utilities/Network Utility.app
    Google Chrome:
      Version: 12.0.742.122
      Last Modified: 7/8/11 8:30 PM
      Kind: Intel
      64-Bit (Intel): No
      Location: /Applications/Google Chrome.app
... just a PERL script away from being a spreadsheet.

I need help with closing a running program. It seems like it does not count as a program. Tried to turn of the computer and closing all programs. Please help!?

I have a problem with a grey text box. It writes and says all i do. For example: When i now write it says all the letters one for one. If i open a new rogram it says so. If i click on something it gives me information about it. I can click the box and drag it, but dont close it. I have restarted the computer and closing all windows and programs. It just popped out when i was pressing some buttons on the mac. I think it is a easy way to fix it, but i cant find out what it is named and search for it. I think it is made for help and i did not download anything to get it. If i change user on the mac it does go away when I am on the other user, but i really want to keep the one i have because off all the settings and programs i have.
Please reply if you know anything about this.
This is a printscreen of the box, the language is Norwegian if someone wonder...
It is really annoying, I hope someone can help me out.

Oh thanks alot! Really happy that people take the time to answer my `noob`questions! Would not find that out by my own.
Thanks!

Need a way to stop debug pop-up

Hi,
I once found an article on how to stop the debugger window from popping up every time I refresh the window. Does anyone know where that article is or know how to stop the window from coming to the front every time? I still want to use the debugger in a pop up window, but I just don't want it to come to the top every time I reload. Thanks.

Try adding _cf_nodebug=true as a url param to the page. That should block debug for a given request.

Run Program in background

Hi
I know there is a post about this already in the newsgroup but I think I
need something different.
I need a way to make my program completely invisible to my users basically
have it running as a service. I can't for some reason remove the FP in the
app builder of my toplevel vi, I don't know why. And anyway, would removing
the FP in the app builder also remove the vi in the taskbar? Does anyone
know how to do this?
Thanks
Jacob Thastrup

The program is for a Win2K/NT4 enviroment. I have never herd of a Win2K/NT4
command/program called "Xvfb". Do I need to use a different command or can
I send the display to another place?
Thanks
Jacob Thastrup
[email protected] (Ricardo Leal) wrote in
<[email protected]>:
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Jacob Thastrup wrote:
>
>> Hi
>>
>> I know there is a post about this already in the newsgroup but I think
>> I need something different.
>> I need a way to make my program completely invisible to my users
>> basically have it running as a service. I can't for some reason remove
>> the FP in the app builder of my toplevel vi, I don't know why. And
>> anyway, would removing the FP in the app builder also remove the vi in
>> the taskbar? Does anyone know how to do this?
>>
>> Thanks
>>
>> Jacob Thastrup
>
>Jacob:
>
>I tryied to hide the front panel with labview application builder for
>linux but it doesn't remove the front panel. I got this
>in Linux, you must create a virtual frame buffer first and then send the
>graphical out of labview to this virtual x-window.
>
>For create the virtual frame, execute the following command:
>
>Xvfb :1 -screen 0 160x120x16 &
>
>with this you create a virtual frame buffer of 160x120 and 16 bits, then
>you must send the application to this x-window:
>
>Application -display :1 &
>
>With this you can execute a program whithout graphical out and also you
>can mantain in background with nohup command.
>
>
>
>--
>*********************************************************
>Ricardo Leal Pacheco.
>e-mail: [email protected]/[email protected]
>FONO: (09)7111100, 654622.
>INGENIERIA CIVIL ELECTRONICA U.T.F.S.M
>*********************************************************
>
>
>
>--------------25B9B630C9B3D0B8D29F4A83
>Content-Type: text/html; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>
>
>Jacob Thastrup wrote:
>Hi
>I know there is a post about this already in the newsgroup but I
>
>I
>
need something different.
>
I need a way to make my program completely invisible to my users
>have it running as a service. I can't for some reason
>
>in the
>
app builder of my toplevel vi, I don't know why. And anyway, would
>removing
>
the FP in the app builder also remove the vi in the taskbar? Does
>know how to do this?
>
Thanks
>
Jacob Thastrup
>Jacob:
>I tryied to hide the front panel with labview application builder for
>linux but it doesn't remove the front panel. I got this
>
in Linux, you must create a virtual frame buffer first and then send
>the graphical out of labview to this virtual x-window.
>
For create the virtual frame, execute the following command:
>
Xvfb :1 -screen 0 160x120x16 &
>
with this you create a virtual frame buffer of 160x120 and 16 bits,
>then you must send the application to this x-window:
>
Application -display :1 &
>
With this you can execute a program whithout graphical out and also
>you can mantain in background with nohup command.
>
>
>
>*********************************************************
>Ricardo Leal Pacheco.
>e-mail: [email protected]/[email protected]
>FONO: (09)7111100, 654622.
>INGENIERIA CIVIL ELECTRONICA U.T.F.S.M
>*********************************************************
>
>
>--------------25B9B630C9B3D0B8D29F4A83--

Stopping a program in debug mode

Hi all,
i have am having a intermitent issue with a program. first let me give you the issue and then the specs.
This is an inconsistant program lockup. when the program runs in an, .exe format it runs fine for an hour to a couple of days and then goes to a white screen and freezes. the program is basically just continiously reading a DAQ card and comparing readings to set values.
if i have the program running in Debug mode thru CVI and it freezes, CVI sees it as running (in top left hand corner of CVI interface), if i push the stop button (break execution) the break execution dims but the program never stops and the Running indication is still active.
question--- is there another way to stop the program while it is in this frozen state to see where the issue is hanging up. like a hard stop command ????
I can only stop the program by using task manager and ending CVI there. which does me no good in finding the freezing point.
CVI 2012 sp1
with a PCI 6071E DAQ

There isn't an easy way to debug this kind of events.
The behaviour you are seeing (stop button dimmed after click but program that soesn't stop) normally happens when the program is stuck in a operation waiting for it to finish before breaking into the IDE. It may be a popup message waiting for user input, a I/O operation with a long or infinite timeout...
To deal with such a kind of thing you can for example write operations to a log file -one line before each critical call and one after that- so that you can at least see where it hanged. Alternatively you can use DebugPrintf to write messages to the debug output window: if in the IDE you have this window listed in Windows menu, if an .exe you can use utilities like DebugView to receive those messages. Another alternative can be to use Remote Debugging.
However, this is only a list of possible instruments and techniques: solving these problems usually ends up in a boring task of trial and error to narrow down to the critical situation and trying to overcome it.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Ways of debugging standard program

ways of debugging standard program to find out the solution!

Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
Decide whether you want to set a local or global watchpoint.
Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator
Meaning
<
Less than
<=
Less than or equal
=
Equal
<>
Not equal
=
Greater than or equal
Greater than
You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR
Only one of the specified conditions must be met
AND
All of the conditions must be met.
Changing Watchpoints
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list. The following dialog box appears:
Choose the pencil icon in the line containing the watchpoint you want to change.
Change the watchpoint attributes in the Create/Change Watchpoint.
Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint ® Delete or Breakpoint ® Deactivate/activate. Instead, proceed as follows:
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
&objectname
Displays the references of strings, internal tables as well as data and object references
*itab
Displays the table header of the internal table itab
Example
If a watchpoint is set for the object in question at runtime, the program is stopped as soon as the reference is changed. A short dump can be intercepted in this way to stop the program being terminated when the memory is overwritten.
Analyzing Source Code
The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways. For further information, refer to Stepping Through the Source Code
For information about functions within the source code display, see Displaying the Source Code
There are also different display modes that provide various information and display the contents of individual fields, tables, and so on:
Reward if usefull

I own CS4, upgraded to CS5, then joined CS6, CC... and now I installed CC14. Which will be the best way to delete or uninstall the programs I don't need keeping only CC14 without running into issues? I have an Alienware Area 51 PC running Windows 7.

I own CS4, upgraded to CS5, then joined CS6, CC... and now I installed CC14. Which will be the best way to delete or uninstall the programs I don't need keeping only CC14 without running into issues? I have an Alienware Area 51 PC running Windows 7.

Which will be the best way to delete or uninstall the programs I don't need keeping only CC14 without running into issues?
There is none. Whatever you do to get rid of the older versions will inevitably do damage to shared components and other stuff of the new versions as well. That's just how it is with this approach... Uninstall the older versions, run the cleaner tool then reinstall CC 2014.
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
Mylenium

I need help finding a workable web program that is not CSS based. I tried IWeb and it just won't work for me. Way too limiting. I've been using a 12 year old copy of Macromedia Dreamweaver, but the new Dreamweaver is CSS

Been building web pages for nearly 20 years, starting with GoLive. Went to Dreamweaver about 12 years ago, the Macromedia version. Tried going to iWeb when it came with a new Mac, but found it way too limiting with it's CSS template base.   Unknowlingly, I then bought a new copy of Dreamweaver.   Ooops, Adobe had bought Macromedia and Dreamweaver, too, is now CSS based, which for my money makes it useless to anyone who likes simplicity.   Now I find that even iWeb has been discontinued. I was told yesterday that Apple doesn't have a web program any more.   At 12 years old, I just don't think it's practical to try to load my old Macromedia Dreamweaver into the new Mountain Lion (I'm getting a new Mac), though it is running, barely, in Snow Leopard.
I need to find a web builder program that will permit simple construction of educational pages, nothing fancy, nothing artistic, just create a page, give it a color, type or drag in text, insert a table, insert pix in the table blocks, add text under the pix... done!    I should note that I am not looking to build traffic. I teach simple things for free and people who want to learn those things (antique sewing machine repair, quilting, building longbows) find me.
I've downloaded trial versions of half a dozen or so programs and looked at maybe 20 more, but all are either CSS based and drive me insane with requirments for constantly making rules and template models, and/or require that you base your web presence in their server.   Also, many will not work with pages built in other programs. I maintian a volume of over 1000 web pages, many requiring regular updating, and they have been with the same server for more than 15 years. I'm not about to change.
So, anybody know a simple, old fashioned web builder that's happpy on a Mac platform?
Captain Dick

Although not supported anymore, iWeb does still function using Mountain Lion...
http://www.iwebformusicians.com/iWeb/mountain-lion.html
... and you can purchase it from Amazon.
Start with a blank page using the Black or WHite template.
All modern websites use CSS and there are thousands of free templates to be had if you want to use a code entry style application. You will need to go this route if you want to create a site that is viewable on mobile devices although you can create an iPhone version using iWeb...
http://www.iwebformusicians.com/iWeb/Mobile-iWeb.html
Search this forum for numerous topics about iWeb alternatives.

Need a way to stop running programs

Similar Messages

Maybe you are looking for