Dbx to debug JNI programs stops on SIGUSR2

Hello,
I am debugging a C program that uses the Java Virtual Machine throught the JNI interface.
When using dbx to debug the program, dbx keeps on stopping on SIGUSR2 and SIGSTOP signals that are delivered to the process. I would like to ignore those an concentrate on the code I am debugging. With gdb, I used "handle SIGUSR2 nostop" command to ignore signal handlers.
Could you please help me find a similar function in Dbx.
Thank you in advance
Marwan Khalil

Similar Messages

Help me!! i don't know how to debug jni program!!

i have finished a jni program. but when i run the java project, some errors appeared.
for i am sure the errors come from the native method ,i set a breakpoint on the native call and debug the project. for the jni program were written with c++, so when i choose "step into" , it dosen't step into and just report some kinds of error.
i use jbuilder4.0 for java program and vc++6.0 for the native method.
i had try two ways. i try to invoke the JVM in native method but i failed to set the classpath. and i debug the native method , the dll, and link to the java.exe. but there is no place to input my classname when load the java.exe. what the result is some information of java.exe.
can anybody help me??!!!!

Make sure your Active Configuration is set to Debug.
Then make sure you are loading the dll from the Debug directory in your Java application. Set all the Breakpoints etc you want in your DLL, build it.
Start your java application from the command line (you do not need it in debug mode at all if you only want to debug the DLL. Make sure you have some way of causing the App to wait for some interaction so you can do the following.
In your open CV++ project select Build->Start Debugging->Attach to Process. Attach to the process that is the java VM running your App.
The cause your Java app to run normally.
Breakpoints etc will cause the VC++ debugger to be invoked and you can merrily debug to your hearts content.

SoS, windows freezing when debugging jni code

Somebody Help!!!!
I am desperately trying to debug JNI code with MSDEV debugger.
This is a flow:
1. I run the java application from Msdev. Visual 6.0
2. Insert a breakpoint in the first native method.
3. The program successfully stops in the breakpoint.
4. The "next" debugger command freezes WINDOWS :(
I have tried all last jdk2 releases starting from 1.3 till 1.5.
Any ideas ?
10000000x in advance

Cross-post:
Duplicate post:
http://forum.java.sun.com/thread.jspa?threadID=604754
@OP: QUIT IT!

Adobe AIR Debug Launcher has stopped working Error on Flash Builder 4.6

Hi,
Maybe you could help me out here as I’ve search the web and Adobe forum but could not find any answer.
I just installed Flash Builder 4.6 (after uninstalling 4.5.1), now when I run my app, the adl.exe crashes (error details below). I thought because I have an app that was created with 4.5, but then I created a new app with this version and it still crash. I have Windows 7 64-bit PC.
Thanks so much. Any help is greatly appreciated.
Error details:
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     adl.exe
Application Version:     3.1.0.4880
Application Timestamp:     4eb7612e
Fault Module Name:     Adobe AIR.dll
Fault Module Version:     3.1.0.4880
Fault Module Timestamp:     4eb75fb9
Exception Code:     c0000005
Exception Offset:     000a8a5b
OS Version:     6.1.7600.2.0.0.256.48
Locale ID:     1033
Additional Information 1:     0a9e
Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
Additional Information 3:     0a9e
Additional Information 4:     0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0×0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
And this is the crash log:
Version=1
EventType=APPCRASH
EventTime=129672424273270780
ReportType=2
Consent=1
ReportIdentifier=3f7d7727-1c55-11e1-a8fc-705ab656b183
IntegratorReportIdentifier=3f7d7726-1c55-11e1-a8fc-705ab656b183
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=adl.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.0.4880
Sig[2].Name=Application Timestamp
Sig[2].Value=4eb7612e
Sig[3].Name=Fault Module Name
Sig[3].Value=Adobe AIR.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.1.0.4880
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eb75fb9
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000a8a5b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
UI[3]=Adobe AIR Debug Launcher has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[15]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\msi.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\IMM32.DLL
LoadedModule[19]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[20]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[21]=C:\Windows\syswow64\NSI.dll
LoadedModule[22]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\runtimes\air\win\Adobe AIR\Versions\1.0\Adobe AIR.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\system32\WINMM.dll
LoadedModule[26]=C:\Windows\system32\OLEACC.dll
LoadedModule[27]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[28]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[29]=C:\Windows\system32\MSIMG32.dll
LoadedModule[30]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 5.82.7600.16661_none_ebfb56996c72aefc\COMCTL32.dll
LoadedModule[32]=C:\Windows\syswow64\WININET.dll
LoadedModule[33]=C:\Windows\syswow64\urlmon.dll
LoadedModule[34]=C:\Windows\syswow64\iertutil.dll
LoadedModule[35]=C:\Windows\system32\mscms.dll
LoadedModule[36]=C:\Windows\system32\USERENV.dll
LoadedModule[37]=C:\Windows\system32\profapi.dll
LoadedModule[38]=C:\Windows\system32\Secur32.dll
LoadedModule[39]=C:\Windows\system32\DSOUND.dll
LoadedModule[40]=C:\Windows\system32\POWRPROF.dll
LoadedModule[41]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[42]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[43]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[44]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[45]=C:\Windows\system32\WINNSI.DLL
LoadedModule[46]=C:\Windows\system32\DNSAPI.dll
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\system32\dbghelp.dll
LoadedModule[49]=C:\Windows\system32\uxtheme.dll
LoadedModule[50]=C:\Program Files (x86)\MMTaskbar\shellhook.dll
LoadedModule[51]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[52]=C:\Windows\system32\mlang.dll
LoadedModule[53]=C:\Windows\system32\dwmapi.dll
LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 6.0.7600.16661_none_420fe3fa2b8113bd\comctl32.dll
LoadedModule[55]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[56]=C:\Windows\system32\apphelp.dll
LoadedModule[57]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\DropboxExt.14. dll
LoadedModule[58]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCP71.dll
LoadedModule[59]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCR71.dll
LoadedModule[60]=C:\Windows\system32\EhStorShell.dll
LoadedModule[61]=C:\Windows\system32\PROPSYS.dll
LoadedModule[62]=C:\Windows\system32\ntshrui.dll
LoadedModule[63]=C:\Windows\system32\srvcli.dll
LoadedModule[64]=C:\Windows\system32\cscapi.dll
LoadedModule[65]=C:\Windows\system32\slc.dll
LoadedModule[66]=C:\Windows\system32\credssp.dll
LoadedModule[67]=C:\Windows\SysWOW64\schannel.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Adobe AIR Debug Launcher
AppPath=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe

Dear, I had the same problema.
Was the sandbox from firewall.
I disabled and worked.

Relating debugging of program.

hi experts.
i want to learn
how to do debug of program.
how to use break point.
how to use watch.
how to debug selection-screen and module pool programming.
please help it is very urgent.
give some link also.

HI
    Debugger
The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.
Two types of debugging are currently possible: Debugging with the classic Debugger for release levels up to and including 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:
·         The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.
The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means.
The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.
As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the Debugger at any time during a session under the menu option Debugging.
As of Release 7.00, the new ABAP Debugger is the default.
Breakpoints
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing 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 Debugger is activated when the program reaches this point.
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 more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. 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 program execution is always to be interrupted at the same place. For more information, refer to the chapter 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 more information, refer to the chapter 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 remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, 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.
For further information on special breakpoints, refer to:
Breakpoints at Statements
Breakpoints at Subroutines
Breakpoints at Function Module Calls
Breakpoints at Methods
Breakpoints at System Exceptions
    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 under which a watchpoint is to become active.
·        You can specify a logical link for up to five (conditional) watchpoints.
See also Specifying Logical Links.
·        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
REWARD IF HELPFUL
vivekanand

Exception Occur while Using Microsoft Visual Studio for Debugging JNI app.

Hi all,
My JNI program works fine. And also Visual Studio IDE allow to debug C++ program properly.
But after each instance of program executation(Under Visual Studio IDE) I am getting following log file.
================================================================================================================
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d99f278, pid=4800, tid=1196
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b06 mixed mode)
# Problematic frame:
# V [jvm.dll+0x12f278]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
--------------- T H R E A D ---------------
Current thread (0x00446c00): JavaThread "main" [_thread_in_vm, id=1196]
siginfo: ExceptionCode=0xc0000005, reading address 0x545c3a49
Registers:
EAX=0x545c3a45, EBX=0x00000000, ECX=0x004475c8, EDX=0x01bdf6a8
ESP=0x01bdf69c, EBP=0x00447594, ESI=0x00446c00, EDI=0x00447594
EIP=0x6d99f278, EFLAGS=0x00010202
Top of Stack: (sp=0x01bdf69c)
0x01bdf69c: 00447598 00446c00 000000b6 004475c8
0x01bdf6ac: 004475c4 004475c0 004475bc 6d99f3d1
0x01bdf6bc: 01bdf720 00447594 00447598 00000e00
0x01bdf6cc: 00446c00 6d92a997 01bdf720 00447594
0x01bdf6dc: 00447598 00000e00 000000b6 00446c00
0x01bdf6ec: 00446c00 07e73fd9 01bdf768 000000b6
0x01bdf6fc: 00446c00 00446c00 01bdf700 01c67cb4
0x01bdf70c: 01bdf768 01bdf708 00447158 00447160
Instructions: (pc=0x6d99f278)
0x6d99f268: 4a 57 8b 7c 24 24 3b fb 75 04 33 c0 eb 05 8b 07
0x6d99f278: 8b 40 04 50 56 8d 4c 24 38 e8 fa 89 ed ff 8b 4c
Stack: [0x01b90000,0x01be0000), sp=0x01bdf69c, free space=317k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x12f278]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j FILE_INFO_J.SetOutputFileName(Ljava/lang/String;)V+1
v ~StubRoutines::call_stub
j FILE_INFO_J.ReadBinaryFile(Ljava/lang/String;LFILE_INFO_J;)V+0
j FILE_INFO_J.CopyBinaryFile(Ljava/lang/String;)V+3
j FILE_INFO_J.main([Ljava/lang/String;)V+38
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x0be19c00 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=3888]
0x0be18000 JavaThread "CompilerThread0" daemon [_thread_blocked, id=3752]
0x0be0cc00 JavaThread "JDWP Event Helper Thread" daemon [_thread_blocked, id=1336]
0x0be09800 JavaThread "JDWP Transport Listener: dt_socket" daemon [_thread_in_native, id=4848]
0x0bdfbc00 JavaThread "Attach Listener" daemon [_thread_blocked, id=4160]
0x0bdfac00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1436]
0x0bde8000 JavaThread "Finalizer" daemon [_thread_blocked, id=676]
0x0bde6c00 JavaThread "Reference Handler" daemon [_thread_blocked, id=4516]
=>0x00446c00 JavaThread "main" [_thread_in_vm, id=1196]
Other Threads:
0x0bde3800 VMThread [id=4640]
0x0be34c00 WatcherThread [id=5112]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 960K, used 17K [0x03cd0000, 0x03dd0000, 0x041b0000)
eden space 896K, 2% used [0x03cd0000, 0x03cd47c8, 0x03db0000)
from space 64K, 0% used [0x03dc0000, 0x03dc0000, 0x03dd0000)
to space 64K, 0% used [0x03db0000, 0x03db0000, 0x03dc0000)
tenured generation total 11948K, used 7985K [0x041b0000, 0x04d5b000, 0x07cd0000)
the space 11948K, 66% used [0x041b0000, 0x0497c5b8, 0x0497c600, 0x04d5b000)
compacting perm gen total 12288K, used 1690K [0x07cd0000, 0x088d0000, 0x0bcd0000)
the space 12288K, 13% used [0x07cd0000, 0x07e76a30, 0x07e76c00, 0x088d0000)
No shared spaces configured.
Dynamic libraries:
0x00400000 - 0x00423000      C:\Program Files (x86)\Java\jdk1.6.0_02\bin\java.exe
0x7d600000 - 0x7d6f0000      C:\WINDOWS\system32\ntdll.dll
0x7d4c0000 - 0x7d5f0000      C:\WINDOWS\syswow64\kernel32.dll
0x00350000 - 0x003eb000      C:\WINDOWS\syswow64\ADVAPI32.dll
0x7da20000 - 0x7db00000      C:\WINDOWS\syswow64\RPCRT4.dll
0x7d8d0000 - 0x7d920000      C:\WINDOWS\syswow64\Secur32.dll
0x7c340000 - 0x7c396000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\msvcr71.dll
0x6d870000 - 0x6dab9000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\client\jvm.dll
0x7d930000 - 0x7da00000      C:\WINDOWS\syswow64\USER32.dll
0x7d800000 - 0x7d890000      C:\WINDOWS\syswow64\GDI32.dll
0x76aa0000 - 0x76acd000      C:\WINDOWS\system32\WINMM.dll
0x7dee0000 - 0x7df40000      C:\WINDOWS\system32\IMM32.DLL
0x6d3c0000 - 0x6d3c8000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\hpi.dll
0x76b70000 - 0x76b7b000      C:\WINDOWS\system32\PSAPI.DLL
0x6d4b0000 - 0x6d4d9000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\jdwp.dll
0x6d770000 - 0x6d776000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\npt.dll
0x6d820000 - 0x6d82c000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\verify.dll
0x6d460000 - 0x6d47f000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\java.dll
0x6d860000 - 0x6d86f000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\zip.dll
0x6d330000 - 0x6d337000      C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\dt_socket.dll
0x71c00000 - 0x71c17000      C:\WINDOWS\system32\WS2_32.dll
0x77ba0000 - 0x77bfa000      C:\WINDOWS\syswow64\msvcrt.dll
0x71bf0000 - 0x71bf8000      C:\WINDOWS\system32\WS2HELP.dll
0x10000000 - 0x10023000      C:\WINDOWS\system32\nvappfilter.dll
0x77670000 - 0x777a9000      C:\WINDOWS\syswow64\ole32.dll
0x0c150000 - 0x0c1db000      C:\WINDOWS\syswow64\OLEAUT32.dll
0x7db30000 - 0x7dbb0000      C:\WINDOWS\system32\mswsock.dll
0x5f270000 - 0x5f2ca000      C:\WINDOWS\system32\hnetcfg.dll
0x71ae0000 - 0x71ae8000      C:\WINDOWS\System32\wshtcpip.dll
0x7df50000 - 0x7dfc0000      C:\WINDOWS\system32\uxtheme.dll
0x4b3c0000 - 0x4b410000      C:\WINDOWS\SysWOW64\MSCTF.dll
0x777b0000 - 0x77833000      C:\WINDOWS\system32\CLBCatQ.DLL
0x77010000 - 0x770d6000      C:\WINDOWS\system32\COMRes.dll
0x77b90000 - 0x77b98000      C:\WINDOWS\syswow64\VERSION.dll
0x0c500000 - 0x0c7c5000      C:\WINDOWS\system32\xpsp2res.dll
0x75da0000 - 0x75e5d000      C:\WINDOWS\system32\SXS.DLL
0x0cc60000 - 0x0ccc1000      E:\TI\Assignment_3\JNIFileOperation_C\Debug\JNIFileOperation.dll
VM Arguments:
jvm_args: -Xrunjdwp:transport=dt_socket,server=y,address=8888,suspend=n
java_command: FILE_INFO_J E:\Assignment_3\VC.pdf
Launcher Type: SUN_STANDARD
Environment Variables:
PATH=D:\oracle\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Subversion\bin;C:\Program Files (x86)\Java\jdk1.6.0_02\bin;C:\Program Files (x86)\Java\jdk1.6.0_02\jre\bin\client;C:\Sun\SDK\bin;��!
USERNAME=user
OS=Windows_NT
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 47 Stepping 2, AuthenticAMD
================================================================================================================
So please tell anyone could Figure out what is this file all about??
Is this says to be worry about it .. or just provide information of current system status??
I will be obliged to you if you would help me
Thank you.

This is exactly due to the memory stack.This error is entirely due to the native code.Check the native code,if there are data conversions handle them carefully
and if you are passing an array see to that the array doesnt oveflow.
Have some prints in the native code and watch the data transferred

Debugging the program that will get triggered for a particular output type

Hi all,
I have one program,which will get triggered when a Sales order of type 'VOR' is created.Whenever 'VOR' order is created it will trigger the 'ZALT' output type.And this output type 'ZALT'has been configured to my program.This output type configuration has been set up by my functional consultant.
My problem is I created Sales order of type 'VOR'.But I want to debug my program,which has to be triggered because of that 'VOR' sales order type,which in turn triggers 'ZALT' output type and in turn triggers my program.
My problem is I created Sales order of type 'VOR' by keeping debugging point in my program.But it is not going to my program and simply displaying sales order has been saved.
So is the outtype has been configured properly?.Do I need to go to my functional consultant?Could anyone explain in this regard?
Rgds,
Balaji

Hi Balaji,
If possible, try to repeat the output in the output type messages screen of VA02 and change its dipatch time to '1'(Through further data). Now put the break point in the program assigned to output tye 'ZALT'(You can see this in the TNAPR table) and run the program RSNAST00 through SE38. The program will stop at the break point.
If its not possible to repeat the output and if you want to check it the first time the output type is processed, ask the functional consultant to change the dispatch time in the condition record that is being retrieved for proposing the output type to '1'. Now run RSNAST00. The program will stop at the breakpoint.
Thanks,
Vinay

Debugging driver program for SAP SCrIPT

Hi,
I am using a z report for creating handling units.As soon as the handling units are created the spool is genearted for all the handling units and the spool requests are visible in SP01.However the print ouput is having some error.I want to debug the driver program.Fronm nace I found out the driver program and have placed break-point in the form routine Entry sapscript and also activated thhe debugger for te concerned SCript,but the debugger is not stopping .
Also I have checked the script name from the spool.
Kindly guide where is the problem and how to proceed.Any help will be acknowledged.
Regards,
Abhishek

HI,
Write a infinite loop in the diver program before u call the open form or before the statement from where you want to debug.
set the infinite loop by this code.
data no type i value 1.
while no eq 1.
endwhile.
break-point.
Then after inserting this code activate and run the program, then run the transaction after runing the transaction ,
goto TCODE ->SM50 u will see list of program select the driver program then select program/session from menu then select program->debugging, then your debug will start from the infinite loop , then change to 2 , then u can debug the program.
Hope this helps.
Regards,
Madhukar Shetty

Not able to debug z program attached to special funtion in processing routi

Hi,
I want to debug my z pogram. attached to special funtion in processing routine.but not able to debug But debugger is not passes through that z program if i passes through transaction vl02n.
Regards,
Ranu.

Hi Sharma,
if the output type is triggered automatically and sheduled background and creating spool or sending mail.
then try this way.
Write the statemnet in your program to debug the program in Background.
data : w_flag type C.
do.
if w_flag = 'X'.
exit.
ENDIF.
enddo.
and execute the VL02n and go to t-code SM50 and select your program and got to menu >program->program> Debug
the the program stops in your Zprogram and make the w_flag to 'X' and continue debuggin zprogram.
Regards,
prabhudas

HelloWorld JNI program Generating DLL

I am trying to run the HelloWorld JNI program.
I have generated the helloworld.h file.
I am using VC++ to create a DLL.
The c program in VC++ refuses to recognize jni.h or even helloworld.h
Is there any other way to generate a DLL , or if someone has faced a similar situation,please suggest.
I am new to JNI.
I have added jni.h and helloworld.h files in the project and also copied these and other header files in the include directory of VC++.
Thanks in advance,
Ann

Hi,
The dll in vc++ has a default folder structure
In the project space (let us assume u named the dll project in vc++ as hello) ----- there will b a debug folder inside the hello folder which also will contain some other files
Now copy the .h file u created (hello.h) along with jni.h and jni_md.h (these u can search in j2sdk bin) and paste it into the hello folder (the vc++ env).... (not into the debug folder)
U also have to add these files in ur vc++ env (by using the add to project--files option in the menu). These files will b automatically added into the header files
Now when u build the vc++ proj it will create the dll file (eg..hello.dll) which will b put in the debug folder
Now copy that dll file and paste it in the java workspace (where the hello.java file is located)
Now executing the java file will give u the JNI results
Manoj

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

Not able to open adobe XI Pro after I have filled out a documents and trying saving it. The program stops working & won't open up again. Tried to complete a repair, rebooting nothing works. Help please.

Not able to open adobe XI Pro after I have filled out a documents and trying saving it. The program stops working & won't open up again. Tried to complete a repair, rebooting nothing works. Help please.

Hi,
Can you pls. provide more details of the issue?
OS/Platform
It would be great if you can provide the MSI logs for repair from the %temp% directory.
Thanks,

How to debug a program which is running in background (Job)

Hi,
I have a program which can be run only in background. I have to debug that program. Could you please let me know, how can I do that?
Thanks,
Sandeep

basic FAQ, please search before asking.
Thread locked.
Thomas

How can i debug a program attached with a Job schedule ?

Hi experts,
In a background job one program plus one variant is attached, now I don't have any authorization of SE38. I want to debug the program. How can it be possible?
Thanks in Advance,
Abhijit

Hi
GOTO SM51.
There choose the server in which ur background program is running. Place the cursor on the line which shows your program. Choose the menu option 'Debugging'.
Depending on your version the menu option is in different places.
If you have the correct authorizations, a window pop will pop up, with your program in the debugger.
Regards,
Vishwa.

Adobe Photoshop Element 10 Program Stops (i.e, Crashes)

I currently have a large number of photographs stored in Elements 10 (this may be referred to as the catalogue). When I try to edit a photograph, the program stops working when I close or save the edited photograph and try to go back to the Organizer. Someone mentioned that I may have too many photographs stored in Elements 10. I thought that I could keep and back-up unlimited photograhs without affecting the functionality of the Elements 10 program.
Do I need to reduce the number of photographs I have in Elements 10 to improve the functionality of the program? Where or how do I store these photographs, some of which have been edited with Elements 10, for future use?

Hi ...
If you have anti virus software installed, you need to disable that in order to download apps.
Apple's policy clearly states that, "all sales are final" > iTUNES STORE - MAC APP STORE - TERMS AND CONDITIONS
edited by: cs

Dbx to debug JNI programs stops on SIGUSR2

Similar Messages

Maybe you are looking for