NetConnection Debugger and FMS2
Hello everybody,
maybe I am to stupid or totally blocked to see what I do
wrong.....
I'd like to use the NetConnection Debugger with FMS2 in
Flash8.
From several Forum posts I lgot out to place the Remoting
Classes and the RemotingDebug
Classes from the library on the stage.
Then I do the following in AS 2:
import mx.remoting.debug.NetDebug;
import mx.remoting.NetServices;
import mx.remoting.*;
import mx.rpc.*;
import mx.remoting.debug.*;
import mx.services.Log;
NetDebug.initialize();
So far, so good... To test it out I placed a
NetDebug.trace("Starting up"); Statement (Just to see if NCD
is responding).
"NetDebug.trace();" prints the "Starting up" - Message into
the (running) NetConnection debugger.
But, when I go further in my code, doing a NetConnect() or
anything else, there is only silence at NCD.
It is silent as a fish regarding to log FMS-Messages, but on
the other Hand it reports AMF ( against ColdFusion) very well.
So I rather think I am not importing the necessary classes,.
But wich are they ???
What is missing in my above code to make NCD log against FMS
in Flash8 ?
I checked the Manuals and Livedocs, but found fitting no
answer, yet.
Wich classes do I have to import to make NCD log FMS-Messages
and errors ?
Thanks in advantage for any enlighting answer
Greets MIBtwo
Hi,
Can you please post a little more detail on how are you using the NetConnection Debugger so that we can look into this issue better?
Thanks,
Abhishek
Similar Messages
-
Netconnection Debugger not tracing when exporting from Flash 8 with Actionscript 2.0
Ok, Sorry for the long post, but given my research , I wanted
to be clear on the problem and what I have done to address it.---
anyone who has gotten the NetConnection Debugger to work with Flash
8 and actionscript 2.0 on a PC, your help will be greatly
appreciated
When I compile a Flash 8 swf with AS 2.0 the it does not seem
to import the class properly to utilize the net connection
debugger.
I spent a considerable amount of time getting it to work on
My Mac, but on the PC , none of my calls to the debugger are
working.
I have a very simple file that has the following code:
import mx.remoting.NetServices;
import mx.remoting.debug.NetDebug;
NetDebug.initialize();
NetDebug.trace("I am here")
I do not get any errors for the imports, and the files are
where they need to be. ( see the end of the message to see the
directory structure for both the mac and the pc versions of this)
When I first installed the remoting components on my
macintosh, the Net Connection Debugger would not work. I eventually
took my 2004 Classes and overwrote the mx.remoting.debug folder in
the
usr/Library/Application Support/Macromedia/Flash
8/en/Configuration/Classes/mx/
then after restarting flash and the debugger.swf.. it worked
on the mac.
I have tried the same thing on the PC on three separate
machines.
The latest PC is a brand new clean machine.
These are the steps I have followed:
I installed Flash 8 professional
I installed the remoting components
I created a test file with the code from above
I opened the debugger
I exported the file, ............... nothing traced
I then copied the as Class files from my mac and overwrote
the files in the classes directory for mx.remoting.debug
in both these directories.
c:\Documents and Settings\user\Local Settings\Application
Data\Macromedia\Flash 8\en\Configuration\Classes\mx\
and in c:\Program Files\Macromedia\Flash 8\en\First
Run\Classes\mx\remoting.
After a restart of flash and the debugger I am still not
getting a trace out... I am at a loss. I need this to work, and
someone has to have run into this before.
Here is a list of the files in mx\remoting directories on the
Mac and the PC.
Mac
Connection.as
DataGlue.as
debug //this is the folder
----- commands//this is a folder
----- events //this is a folder
----- connectionMixin.as
-----GlobalLocalConnection.as
----- NetDebug.as
----- NetDebugConfig.as
----- NetDebugResponseProxy.as
NetServiceProxy.as
NetServiceProxyResponder.as
NetService.as
Operation.as
PendingCall.as
RecordSet.as
RecordSetIterator.as
RemotingComponentVersion.as
RsDataFetcher.as
RsDataRange.as
RTMPClientResponse.as
Service.as
PC in the Documents and
Settings...............\classes\mx\remoting
Connection.as
DataGlue.as
debug //this is the folder
----- commands//this is a folder
----- events //this is a folder
----- connectionMixin.as
-----GlobalLocalConnection.as
----- NetDebug.as
----- NetDebugConfig.as
----- NetDebugResponseProxy.as
NetServiceProxy.as
NetServiceProxyResponder.as
NetService.as
Operation.as
PendingCall.as
RecordSet.as
RecordSetIterator.as
RemotingComponentVersion.as
RsDataFetcher.as
RsDataRange.as
RTMPClientResponse.as
Service.as
thanks for the help
allen hujsakThank you for the advice. This is still the error I get even
with those two components on stage. Do I have to connect them to
something? I am still trying the same tutorial from
adobe...www.adobe.com/devnet/flash/articles/delta_packet.html
Here's the error...
**Error** Scene=Scene 1, layer=Layer 1, frame=1:Line 1: Error
opening include file NetServices.as: File not found.
#include "NetServices.as"
**Error** Scene=Scene 1, layer=Layer 1, frame=1:Line 2: Error
opening include file NetDebug.as: File not found.
#include "NetDebug.as"
Total ActionScript Errors: 2 Reported Errors: 2
Please help!!!!!! -
NetConnection Debugger in Eclipse?
Hey everyone,
I use the Flex Eclipse Plug-in to develop our applications
and am wondering how to get the NetConnection Debugger working.
I've read this article:
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19355
but it doesn't seem to pertain to the Eclipse plugin. I don't
have a WEB-INF directory or a flex-config.xml. I don't have an
extras directory in my Flex directory either.
Can anyone shed some light on this? FYI--I've never used the
NetConnection debugger before.
Thanks!
AaronAnswering the question myself.. Had to externally open the url from IE..
-
Does anyone know if it is possible to post the messages that
you get in the netconnection debugger to a flash movie that you can
publish to a webpage? I tried importing the netconnection debugger
itself to an fla, but it is protected. I have a user that is having
issues with my Flash application using remoting. I wanted to see if
I could generate a service capture movie that could post the
messages I get in the netconnection debugger into a text box on the
users browser so he could copy and paste it into an email and send
it back to me. Is there anyway to do this in Flash 8 with the AS2.0
remoting classes?/Bump
-
How to use abap debugger and se80
can any body give easy deatils about it?
Hi
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
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: -
PL/SQL Debugger and ORA-12541: TNS:no listener
I installed SQL Developer on my PC (Windows XP). I have a connection to my devlopment database on server (Solaris, Oracle 9.2.0.6).
I create a procedure and compile it successfully. Now I want to 'debug' it. I click on the Debugger (ladybug), set my parameter value and click on 'OK' in the Debug PL/SQL window. In the Debugging log I get:
Connecting to the database Banner devl.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '130.207.xxx.xxx', '4000' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database Banner devl.
What listener is it looking for on my own machine? I don't have J Developer and I'm using a remote database.
I found the thread on setting the 'Prompt for Debugger Host for Database Debugging'. Enabled that and tried debugging again. Got the prompt for entering the IP of the Debugger Host. Tried the database server. So I got:
Connecting to the database Banner devl.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '130.207.xxx.xxx', '4000' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database Banner devl.
The answer is probably right in front of me, but I just can't see it. Is something mission on the database server?I am running SQL Developer on Windows XP Professional and I was experiencing the same problem.
When I started the debugger I got the message from Win XP that Windows Firewall will block some features of the program (being the PC at work I don't have admin privileges on it). I accepted this, not knowing which features would be blocked.
Then, the debugger was just hanging. After a while it timed out and came back with exactly this error message.
I restarted the SQLDeveloper and tried again without much success. This time though I didn't get the Windows Firewall message.
After another few trial and errors I figured out that the Firewall must be blocking connection establishement on the client site i.e. on my PC.
It was the CALL DBMS_DEBUG_JDWP.CONNECT_TCP that was hanging.
As the system admin disabled the Windows Firewall on my PC the debugger started working. We have a luxury to disable local firewalls as there is one that protects our network from outside traffic. People who cannot afford to disable the Windows firewall will have to tinker with the firewall itself and configure it in such a way that it allows traffic on certain port range (4000...4999). Then in SQLdeveloper you will have to go to Tools->Preferences->Debugger and tick Debugging Port Range. The chosen range should match the port range on the Windows Firewall side.
By the way, in the call to CALL DBMS_DEBUG_JDWP.CONNECT_TCP the first parameter is the IP address of your PC and the second one is the port used for debugger connection with the database server. If for some reason the IP address chosen by the debugger is not your IP address (you can find your IP address as follows: Start->Run->cmd; then use command ipconfig), you will have to tick "Prompt for Debugger Host for Database Debugging" on your Debugger Preferences. This way you'll be able to chose the IP address yourself.
Good luck! -
What is a debugger and how do i "unload" it??
When i try to play games that worked well in the past, a window which i never saw before pops up. " debugger found, please unload debugger and try again". What is this?
This question was solved.
View Solution.Hi,
Go to that game forum, they will tell you. Normally I don't bother to do this.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem. -
i have used the debugger and it works great! however, i am a little confused about
how the Smart Data feature works.
my question is ... how do you get "Smart Data" to show up in the Smart Data tab?
the documentation mentions that it displays "Breakpoint Data". how do you set this up?1. Click on a Procedure under the procedures node.
2. The Procedure will be displayed on Right. Click Edit to bring up the code frame for the procedure.
3. On the Code frame set a few break points.
4. Ensure that the procedure is compiled for debug. If not click the Compile for Debug button.
5. Click the debug button
6. When the first breakpoint is hit the Debugging Log is displayed at the bottom of the SQL Developer window.
7. Click on the Smart Data tab.
8. On the Smart Data tab monitor the value of various objects. Verify the Type of these objects.
9. Monitor the value of these objects as the procedure is debugged.
HTH
-Vasan -
Linux Debugger and Debug Player
Hello.
As someone who develops Flash games under linux platform, I'm already struggling that latest version of Flash Player is unavailable for my platform.
For now, there is at least workaround to get 11.2 Debug Player working by replacing libflashplayer.so.
As far, as I understand that would not work with Flash Player 12.
Is there any chance that there will be Debugger and Debug Player 12 released for linux?Jeromie Clark wrote:
We are currently working on a content debugger version of Flash Player for Chrome Pepper, which is the only linux target that is actively supported.
Unfortunately, the debug PPAPI player version is Win/Mac only.
If you have interest in Linux, Flash, AIR, and Scout, feel free to follow my twitter feed and blog.
You can get telemetry data out of the Linux PPAPI Flash Player. Unfortunately,1) it requires starting google-chrome with the --no-sandbox option (I filed a bug on this), and 2) since it's not the debug player, you don't get memory allocation data (you do get the stack profiler and timing data).
Instead, if possible I suggest testing your content under Adobe AIR (under wine on linux), where you get full telemetry data.
You can view this telemetry using Adobe Scout on a Windows VM (if you've paid for Windows and Adobe CC licenses), or with a little cross-platform project of mine called hxScout. -
XSLT producing different results via debugger and xslt.Transform()
I'm producing the body of an email via an xsl. I've been having a problem with the html nested inside a <table> tag not displaying correctly. With a bit of help from the good folks over at the asp.net forums, I've tracked the problem down to getting
different results if I run the xsl via the debugger or via a compiled transform.
When I debug the xsl it produces
<table border="1" cellpadding="4" cellspacing="0" style="..." id="tmsEmailTable">
<tr>
<th width="50%" align="center"><b>Issue</b></th>
<th width="50%" align="center"><b>Resolution</b></th>
</tr>
<tr>
<td>Missing Acknowledgement date</td>
<td><p> Test test</p></td>
</tr>
<tr>
<td>Missing Agent and/or Seller signature</td>
</table>
And that's absolutely correct and displays perfectly if I save the result as an html file. But when I use xslt.Transform(..), where xslt is a compiled transform, it produces
<table border="1" cellpadding="4" cellspacing="0" style="..." id="tmsEmailTable">
<tr><th width="50%" align="center"><b>Issue</b></th><th width="50%" align="center"><b>Resolution</b></th></tr>
<tr>
<td>
Missing Acknowledgement date
</td>
<td></td>
</tr>
</table>
</p><p> Test test</p></td></tr><tr>
<td>Missing Agent and/or Seller signature</td>
<td>
</table>
And to make it even more interesting, that extra </table> tag and the misplaced table data only occur on the first table row, but the table rows are generated by an xsl:for-each.
The relevant bit of the xsl is:
<table border="1" cellpadding="4" cellspacing="0" style="..." id="tmsEmailTable">
<tr>
<th width="50%" align="center">
<b>Issue</b>
</th>
<th width="50%" align="center">
<b>Resolution</b>
</th>
</tr>
<xsl:for-each select="emailbody/checklist/item">
<xsl:if test="string-length(select='issue')>0">
<tr>
<td>
<xsl:value-of select="issue" disable-output-escaping="yes" />
</td>
<td>
<xsl:value-of select="resolution" disable-output-escaping="yes" />
</td>
</tr>
</xsl:if>
</xsl:for-each>
</table>
The code that generates the compiled transform and the (incorrect) output is:
Dim xslt As XslCompiledTransform = New XslCompiledTransform(True)
'Dim xslt As XslTransform = New XslTransform
xslt.Load(templatePath)
Dim objStream As Stream = New MemoryStream(UTF8Encoding.UTF8.GetBytes(xmlData))
Dim strbldrXML As StringBuilder = New StringBuilder()
Dim objXmlReader As XmlReader = XmlReader.Create(objStream)
Dim objXmlWriter As XmlWriter = XmlWriter.Create(strbldrXML)
xslt.Transform(objXmlReader, objXmlWriter)
I've checked that templatePath is pointing to the right file, and the source file I'm debugging the xsl against was copied from the xmlData parameter, so I know the same stuff is getting fed into it.
I've been chasing this for days, and I'm about ready to quit and go get a job at a fast food joint. I'm not wonderful with xsl in general, or xsl in .NET in particular. Somebody PLEASE tell me I'm doing something stupid....
Rebecca M. RiordanThanks for the replay, Fred, but that wasn't the problem.
I still don't know what the problem was, but in putting together a sample for review, I cleaned up the code a little (I inherited this), and while it
appears to be functionally identical, it's working now. Since we're scheduled to go live on Friday, I'm gonna just take the win ;)
In the unlikely event that anybody's curious, the original, non-functional code, looked like this:
Public Function createEmailBody(ByVal templateType As String, ByVal xmlData As String) As String
Dim templatePath, emailBody As String
templatePath = Me.templatePath & "\" & templateType & ".xsl"
Dim xpd As New XPathDocument(New StringReader(xmlData))
Dim xslt As XslCompiledTransform = New XslCompiledTransform(False)
xslt.Load(templatePath)
Dim objStream As Stream = New MemoryStream(UTF8Encoding.UTF8.GetBytes(xmlData))
Dim strbldrXML As StringBuilder = New StringBuilder()
Dim objXmlReader As XmlReader = XmlReader.Create(objStream)
Dim objXmlWriter As XmlWriter = XmlWriter.Create(strbldrXML)
xslt.Transform(objXmlReader, objXmlWriter)
emailBody = strbldrXML.ToString()
Return emailBody
End Function
In cleaning it up, I wrote this:
Public Function createEmailBody(ByVal templateType As String, ByVal xmlData As String) As String
Dim xslt As XslCompiledTransform = New XslCompiledTransform(False)
Dim templatePath As String = Me.templatePath & templateType & ".xsl"
xslt.Load(templatePath)
Dim reader As XmlReader = XmlReader.Create(New MemoryStream(UTF8Encoding.UTF8.GetBytes(xmlData)))
Dim outSB As StringBuilder = New StringBuilder()
Dim writer As XmlWriter = XmlWriter.Create(outSB)
xslt.Transform(reader, writer)
Dim emailBody As String = outSB.ToString()
Return emailBody
End Function
As I said, they look functionally identical to me, but obviously they're not, because the second one works....
Rebecca M. Riordan -
What is the Debugger and how do you turn it off?
Hi folks, I'm updating a site for a client and when I open
the home page
http://www.imcnewcastle.com
I get this annoying pop up from Adobe flash player 10 asking
if my debugger
is on this machine or host application and it locks up if I
try to connect
to local.
What the heck is this and how do I keep it from turning on? I
don't want
browsers to get locked up.
Thanks
Jeff
~~~~~~~~~~~~
Jefferis Peterson, Pres.
Web Design and Marketing
http://www.PetersonSales.comJeff,
> I get this annoying pop up from Adobe flash player 10
asking
> if my debugger is on this machine or host application
and it
> locks up if I try to connect to local.
It's annoying when you don't want to bebug, I agree, but the
situation
you're describing is really useful when you need to debug
Flash content in a
browser. ;)
> What the heck is this and how do I keep it from turning
on?
> I don't want browsers to get locked up.
Assuming you have the FLA source file, open it in the Flash
authoring
tool and head over to File > Publish Settings. Select the
Flash tab, then
uncheck the "Permit debugging" checkbox, then republish the
SWF.
Here's more information on debugging:
AS2
http://www.adobe.com/devnet/flash/articles/debugging_actionscript.html
AS3
http://www.adobe.com/devnet/flash/articles/as3_debugger.html
David Stiller
Co-author, ActionScript 3.0 Quick Reference Guide
http://tinyurl.com/dpsAS3QuickReferenceGuide
"Luck is the residue of good design." -
Debugger and inspect variables
Hi there;
My debugger is some kind crazy,
I've an Integer variable in appmodule's (impl) class, but it shows the variable as it is appModule ( wrong class )
if I print the variable in console it has integer value !!
have any one, saw this before ??
Thanks
Marcos OrtegaSo;
I really think that compiling have some problem here;
I also start to run into
SEVERE: Server Exception during PPR, #1
javax.el.ELException: java.lang.IllegalAccessError: tried to access method com.santoandrea.qvagas.bean_extend.ocorrenciasBean.setViewsDaOcorrencia([Ljava/lang/String;)V from class com.santoandrea.qvagas.bean_extend.ocorrenciasBean_beaVersion0_17
Not at the same procedure, but in other that I have deployed yesterday and no changes was made; At the production server it is working;
My embeded server is raising that IllegalAccessError since today;
About
Oracle JDeveloper 11g 11.1.1.1.0
Studio Edition Version 11.1.1.1.0
Build JDEVADF_11.1.1.1.0_GENERIC_090615.0017.5407
Copyright © 1997, 2009 Oracle and/or its affiliates. All rights reserved.
IDE Version: 11.1.1.1.33.54.07
Product ID: oracle.jdeveloper
Product Version: 11.1.1.1.33.54.07
Marcos Ortega -
Will the debugger work through Citrix and a Aventail connection? I have gotten past the debugger not finding the tns issue.
1. Click on a Procedure under the procedures node.
2. The Procedure will be displayed on Right. Click Edit to bring up the code frame for the procedure.
3. On the Code frame set a few break points.
4. Ensure that the procedure is compiled for debug. If not click the Compile for Debug button.
5. Click the debug button
6. When the first breakpoint is hit the Debugging Log is displayed at the bottom of the SQL Developer window.
7. Click on the Smart Data tab.
8. On the Smart Data tab monitor the value of various objects. Verify the Type of these objects.
9. Monitor the value of these objects as the procedure is debugged.
HTH
-Vasan -
Debugger and formatter disappeared - reverting to previous release
Neither the Debugger or the SQL Formatter are functional in release 0897. The lack of the debugger makes it pretty much useless. I am reverting to the previous release.
You need to examine your QA practices.Yes. It looks like the SQL Formatter only works in the SQL Worksheet, not in the PL/SQL editor for Procedures, Functions or Packages. Also, the formatting of parameter lists for procedures and functions looks a little dodgy.
Cheers
Tim... -
Hi All,
I am having a problem with dates, scripts and the debugger.
I have a procedure that takes a date value as an in_variable.
procedure_x(in_date date)
I usually call this procedure from a script.
select to_date(my_date,'mm/dd/yyyy') into my_var from my table;
proc_x(my_var);
I have set sql developer to run scripts from a specific folder.
So i just type in @runscript.sql
When i do this everything runs perfectly fine.
When I try to debug this procedure by clicking on the debug(inside edit mode) --> run from file
It always returns a date error. 'ORA-01843: not a valid month'
I have noticed in the debugger the date format for some reason defaults to 06-12-01 00:00:00.
I have my nls_date format set to 'MM/DD/YYYY' in the preferences ...
Anybody know what the difference is? I am using the same file and it works when i execute it as an sql script but not when i use the run from file option
Is this a bug in the newest release?
Thanks in advance ...That means that to_date(birth_date,'mm/dd/yyyy') will convert birth_date implicitly to char, to be used for the to_date function.
As you didn't specify any format with to_char, this (implicit) conversion works using the NLS settings.
Now, there's major buggy behaviour (which I reported in NLS bugs when running PL/SQL [fixed] the session created for debugging (or running) a procedure uses the system's defaults instead of the NLS settings in sqldev.
So issuing your call in a worksheet can actually differ from debugging it.
Anyway, this shouldn't be any problem for you here. Why would you want to convert a date to a char to a date?
Only (and always) use to_ functions to convert between different types. So here, you shouldn't...
Regards,
K.
Maybe you are looking for
-
When I try to view the pictures full size it won't go from picture to picture then it locks up.
My iphoto keeps locking up. When I view pictures and double click on them to see them larger it just freezes up and I can't do anything else. I have to quit iPhoto altogether and start over.
-
How to multiple data in the labelProperty of optionsCollection of struts
i have specific problem i have to show the the data in the options as below PUN(pune) MUM(Mumbai) BNG(Banglore) like then BNG is come from different property of the form and Banglore is come from different property of the same form how is it possible
-
I used automator to rename some pages files, and now they can't be opened
I used automator to remove some text from the filenames of a group of pages files, and now they can't be opened. What went wrong?
-
Problem with adding text to photos in PE6 on my iMac
I can't seem to add text to any photo. I have a new iMac, installed PE6, and all other features seem to be working fine. I even reset all tools to default just to be sure I didn't tweak something. When I click on the Text tool and click on a photo, a
-
Cannot register new iPod due to registration screen incorrecltly populating
Hi... trying to register a new iPod, but the main start up screen isn't populating correcly in iTunes. It does not show the entire screen and does not give a scroll bar to be able to scroll to the far right of the screen to click the "register now" b