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.

Similar Messages

[svn] 915: [patch submission] SDK-15042: Check for a previously unpacked player on linux platforms and don' t re-unpack

Revision: 915
Author: [email protected]
Date: 2008-03-25 13:37:13 -0700 (Tue, 25 Mar 2008)
Log Message:
[patch submission] SDK-15042: Check for a previously unpacked player on linux platforms and don't re-unpack
* Took patch verbatim, thanks Tom!
Bugs: SDK-15042
QA: Yes, please test "setup.sh" unpacks correctly on Linux
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15042
http://bugs.adobe.com/jira/browse/SDK-15042
Modified Paths:
flex/sdk/trunk/setup.sh

Revision: 915
Author: [email protected]
Date: 2008-03-25 13:37:13 -0700 (Tue, 25 Mar 2008)
Log Message:
[patch submission] SDK-15042: Check for a previously unpacked player on linux platforms and don't re-unpack
* Took patch verbatim, thanks Tom!
Bugs: SDK-15042
QA: Yes, please test "setup.sh" unpacks correctly on Linux
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15042
http://bugs.adobe.com/jira/browse/SDK-15042
Modified Paths:
flex/sdk/trunk/setup.sh

Video doesn't play in authoring player, does play in debug player

I just updated to CS5 - I'm working on a custom video player. It works fine embedded in a web page both locally and on the network. It works fine in the debug player. However, when I test it in the authoring player I get a NetStream.Play.StreamNotFound error and no video. I have tried setting the Local Playback Security publish settings to both local and network - doesn't find the video either way.
It used to run fine in CS4 in the authoring environment.
Obviously it's hard to debug the problem when it doesn't fail in the debugger. ;-)
Am I missing a setting or ... ?

I just tested the issue with the included Flash video player component which does work fine in the authoring mode.

Debug player is not running, but is installed?

Hi I have installed numerous times the debug player for firefox and also for IE.
But still the regular player is running in the browsers? I uninstalled all players with the uninstall tool but still I get no debug player running in my browser. This way I can't debug my application.
Does anybody know why the player is still the regular one and not the debug player after installing the debug player version?
And does anybody has a solution for it? Is there maybe something I need to do during uninstall or something because until now I have no idea what to do further.
Kind regards.

What's your SWF development environment? Flash Builder, Flash Professional?
I think these applications handle the debugger differently.
Can you please try the following:
Go to C:\WINDOWS\system32\Macromed\Flash. (on 64-bit: C:\Windows\SysWOW64\Macromed\Flash)
Open the mms.cfg file.
Add the following entries:
ErrorReportingEnable=1
TraceOutputFileEnable=1
MaxWarnings=50
Now try to run the SWF file.
Go to the location mentioned above and open the flashlog.txt created.
See if it logs errors.
More info: http://helpx.adobe.com/flash-player/kb/configure-debugger-version-flash-player.html
Thanks,
Sunil

How to test with the standard Flash player, rather than debug player

Folks,
I am interested in running my flexunit 4 tests against the standard flash player, rather than the debug player that comes with the SDK. Is this possible?
BTW, I am working on Windows for now.
I installed both the flash ActiveX control for IE, and the standard flash plugin for Firefox. I then associated the SWF file extension with Firefox using the "Open With" dialog. I had to choose a single program, and the browser appeared to be my only choice, as I could not find any sort of "FlashPlayer10.exe" to associate with. I ran my ant script that calls <flexunit>, and it kind of works. It launches Firefox, runs the tests, and the results get piped back, but Firefox is not shut down. Yep, Firefox stays open after the tests complete. I seem to recall that the debug flash player would close itself after being opened by <flexunit>. I tried using IE, and the same result occurs: the browser is not shutdown after the tests complete. This behavior makes for an unacceptable test setup, as eventually the system memory on the machine will be exhausted as more and more browsers are opened and not closed.
Questions/options:
1) Is there a standard flash player "executable" somewhere on my system that I can associate the SWF files with (that would hopefully shut itself down)?
2) Second choice, is there a way to get the browser to close after <flexunit> completes?
3) or am I stuck using the debug player? I am concerned that testing management at my company might not like the fact that we are testing against a debug player, rather than the standard one that users will likely be using. If flexunit 4 CI only supports the debug player, is there something I can say to appease management?
Thanks for any help...
Trevor

@trevorbutler - Here are my 2 cents, but the group may have a different perspectives for your questions.
Currently, we suggest the use of the CIListener class as a FU4 listener for use when building your test SWF to run via the FU4 Ant task. This class (http://opensource.adobe.com/svn/opensource/flexunit/branches/4.x/FlexUnit4CIListener/src/o rg/flexunit/listeners/CIListener.as) uses the fscommand() function to send a message to its host environment to exit (i.e. - fscommand("quit")). This command is only recognized by the Flash projector and stand-alone players, which are thin wrappers around the Flash Player so that it may be executed as its own process in the OS. Based on the setup you are describing, the behavior you're seeing should be expected since the browser is the host environment for the Flash Player. When the browser recieves the resulting message of the fscommand("quit") call nothing will happen since the browser doesn't support this command. If you use the Flash projector or stand-alone players however, they will exit when recieving the results of this command. The projector/stand-alone players come in two flavors, release and debug. Release will act very closely to the typical plugin installed in the web browser (e.g. - swallows errors, no debug support, etc) whereas debug will allow you to write log files to the system, show error messages, etc. Currently the debug stand-alones are available on Windows, Mac, Linux and the release stand-alone is only available on Linux.
To address your questions:
1. If you've installed the Flash Player browser plugin, there is no way that I know of to launch the player as its own process. I've only had success using the projector/stand-alone player (http://www.adobe.com/support/flashplayer/downloads.html).
2. The Flash Player does have the ability to send javascript to the browser to ask it to close the current window, but most modern browser will prompt the user to confirm they'd like to close the window if its the only open window. Additionally, taking this approach on Mac, the browser process would remain active until an explicit call is made to the host OS to shut down the browser process. The Ant task could be enhanced to use the browser to launch the Flash Player, but that is not currently on our checklist of features to support. If it's something you'd be interested in contributing, let me know and I can work with you on this.
3. For the time being the FlexUnit4 Ant task only supports the stand-alone Flash Player (and adl soon), which for Windows only comes in the debug flavor. The only thing I've run into with the stand-alone player is that ExternalInterface reports that its enabled, but since the host environment is not the browser, javascript calls made via this class will fail, consequently causing tests to fail. I haven't tried anything with shared objects or flashvars but my assumption is that they should work correctly, but anything that depends on the browser has the potential not to.
As far as your testing management goes, I would discuss with them the problem context FlexUnit4 hopes to solve. The framework is intended to produce unit and integration tests. Functional testing is not withing the scope of the library. Although, it's technically feasible to write integration tests which will exercise components similarly to a functional test, tools such as FlexMonkey, Selenium Flex, QTP, etc are much better geared towards this problem domain. Test recording and playback, using these tools, is typically done using the FP browser plugin and is much easier to use by most QA and testing staff. At the end of the day, as we're testing our code using FlexUnit at a smaller granularity than that of which the user interacts with in our application. To reliably test the applicaiton as the user would interact with it requires additional tooling and a different type of testing.
Like I said, just my take, maybe some of the other guys can help as well.

Problem connecting to debug player

I'm at my wits end here. Whenever I try to debug a project I get the error saying that it failed to connect, make sure the debug player is installed. I've gone through all the usual steps and the debugger version of the plugin is defininitely installed. I'm getting the same error whether I use IE or Firefox as the external browser, so it has to be something related to FlashBuilder itself right? I've tried everything I can think of including deleting the .metadat folder and starting fresh. Can anyone shed some light on what's going on here?

This image is the error I get every time I try to run the debugger.
This second image comes a minute or two after the first, regardless of whether I choose "yes" or "no" on the first error.
I am a web design/development student. My Actonscript 3.0 class requires Flash Builder and the debugger. I am already 4 assignmets behind b/c I am unable to get it working correctly. I apologize, but I don't completely understand all of the suggestions posted in the forum. If you could explain them as simple as possible I would really really be grateful. Also, whenever I try to right-click in the running ap, as the last solution instructs, I don't even get the debugger option. This is what I get instead.
I've tried to uninstall/reinstall both Flash Builder and Flash Player without any luck. I really need this resolved asap or I'm afraid I may have to drop this class and honestly speaking, dropping the class is not a viable option. Due to my recent layoff, my school is being funded through the federal TAA program and they have strict timelines about how long I have to complete school. If I drop the class I will miss the deadline. Please, please help me resolve the issue. I am using the latest version Flash Builder available to date, running Windows 7 64bit and the latest version of Flash Player. Originally I just happened to be using Chrome as a browser, but I normally use Firefox. I also have Opera, Safari and IE installed but had the same results when tested in each of these browsers. Again, please make the instructions as simple as possible as I am a web student and don't know much else. Thanks in advance to anyone that can help b/c I desparetly need some help.

IE9 Debugging With Debug Player 11.3 Fails locally

Can someone give me the lowdown on why I can't debug my flash projects locally in IE9 ?
The debug player 11.3 is sucessfully installed, the embed code is sound, the security settings are correct, no active x filtering, and content allowed in security settings. No sandbox issue etc.
Does IE 9 not allow it ?
I usually don't debug in IE9 but since I have it on my machine, Its worthwhile to know what is going on here so any info appreciated.
I SHOULD SAY THAT OF COURSE ONLINE CONTENT WORKS JUST FINE. BUT FLASHBUILDER 4.6 CAN NOT CONNECT IN IE9 TO DEBUGGER. ALL OTHER BROWSERS WORK FINE
WHY?

Yes, works fine in chrome and in firefox with debug player just ie 9 doesnt.
I can assure you I have the debug installed. Tested, and worked with flash some 8 years now so can verify that both with actionscript and by rightclicking >debug,
But Flashbuilder will not connect locally to IE9

Remote compile and debug on Sun Studio

I am currently working with sun studio on my linux station.
is there a way to compile the source code that I edit on the Solaris server using solaris compiler (not Gnu compiler).
Is there a way to debug this program while I'm running the Sun studio session on the Linux.
Currently I have to logon to my server, start studio on it (set DISPLAY to my Linux) and work from the server.
Tnx, Avikosan

I think your question has two parts:
Q: Can I compile on Solaris and generate code that will run on Linux?
A: No. Sun compilers do not support cross-compilation. You must build on a platform compatible with the target. To generate code to be used on Linux, you must build on Linux. Current releases of Sun compilers do not run on or generate code for Linux.
We have "technology previews" of Linux compilers on the Sun Studio web page. These compilers are not released, and are not fully functional. Go to
http://developers.sun.com/sunstudio
click the "downloads" tab, then the "technology preview" menu item.
Q: Can I run the debugger and GUI on Linux?
A: Yes, if you are using Sun Studio 10 or later. The debugger and GUI are available in Linux versions. The Sun Studio 11 version is free. You can get it from the Sun Studio page listed above.

Where is the freakin' 9 Debug player!!

Uh, Yeah
Where is the freakin' flash 9 debug player or stand alone
player for PC's for that matter

surzycki120,
> Hmmm
>
> That makes perfect sense. Very intuitive.
Well sheesh! :-p What do you expect, so shortly after two
worlds
collide? I agree, we're all still reeling a bit in the
aftershock of the
merger (there's an old school pun in there, somewhere). But
patience, dear
fellow (or she-fellow), and keep your chin up. I stand
corrected in part of
my earlier reply. Breaking news indicates that registered
Flash 8
developers may, in fact, download software that allows them
to publish Flash
9 content.
http://www.adobe.com/devnet/flash/articles/flash9_as3_preview.html
I'm downloading at the moment. I should think this software
contains a
debugger.
David
stiller (at) quip (dot) net
Dev essays:
http://www.quip.net/blog/
"Luck is the residue of good design."

Debug button launched non-debug player

Hi all!
I just started working with flash builder 4 today, but for some reason i cant normally use the debug mode.
i want to see all my traces and such so i kinda need it, i think the reason is that the "debug" button launches a non-debug version Flash Player, because on right-click i dont see any of the debug functions. Awhile after opening the window the error about cant connect to Player pops up
When i manually open a debug player the debug function works how it should.
But ofcourse i dont want to open a window each time i want to run it. So my question is, how can i let the debug button run a debug version of the Player? I've tried reinstalling and removing all flashplayers before reinstalling
Thanks already,
Thom

Hi,
I'm assuming you are having trouble launching the debugger standalone binary on Mac. Open Finder, select any SWF file, do a "Get Info" and say "Open with" and point to the debug version of standalone player and choose "Change All".
You can get the debug version of standalone player here: http://www.adobe.com/support/flashplayer/downloads.html
Thanks,
Anirudh Sasikumar
Flash Builder Engineering

How do I update my Flash Debug Player for Flash Builder 4.6?

Hey how do I update my copy of Flash Builder 4.6 to the latest flash debug Player?

Go to flash player downloads and get the latest one for your browser.
http://www.adobe.com/support/flashplayer/downloads.html

MP3 and Flac player

Hi,
I am looking for a good audio player with the option to play MP3 and Flac files.
I have tried FLAC player but its capability for organizing and editing files according to composers and musical works is very limited.
Any help will be appreciated.
Thanks,
Amnon

Flash: I use Adobe 64 bit when absolutely necessary, behind NoScript and FlashBlock (Firefox addons) and sandfox
Audio Player: mplayer (with smplayer frontend), and also VLC
File Archiving: Personally I use a chooser script from within my file manager for most archiving. That way I can do it fast and can customize the script with any archive formats and options I want. Likewise, I use an xtract script associated in my file manager so I can click on any archive and it is instantly extracted into a subfolder - no interaction. Also, if you want 7-Zip support it's p7zip, although I think xz is a more linux friendly and capable implementation of lzma2.
Audio Ripper: Asunder is pretty good, although I'm still shopping.
Video Ripper: I use mplayer, usually through ripdvd
ISO Burner: I wrote a custom script for burning (which I haven't shared) that does it with CLI commands, which I found to be the easiest and most reliable method. Graveman and Brasero are also decent.
PDF Viewer: Evince
You might also check out the list of apps I used to replace KDE when I dropped it.
Welcome to Arch.
Last edited by IgnorantGuru (2010-06-22 02:27:40)

How can I install the Flash Debug Player in Internet Explorer 10?

I just downloaded the Flash Debug Player 11.4.402.287 from http://download.macromedia.com/pub/flashplayer/updaters/11/flashplayer_11_ax_debug.exe - however, trying to install it merely shows a message box saying
The installation encountered errors: Your Microsoft Internet Explorer browser includes the latest version of the Adobe Flash Player built-in. Windows Update will inform you when new versions of the Flash Player are available.
I'm using Internet Explorer 10.0.9200.16384 on Windows 8. A bit of Google research suggested that IE10 has a Flash player built-in (similiar to what Google Chrome has) so I looked for a way to disable the player. It seems that this is indeed possible by clicking the Cogwheel icon in the IE10 toolbar and then selecting 'Manage Add-ons'. The dialog which shows up shows a 'Shockwave Flash Object' entry. However, even with the built-in Flash player disabled, the Flash Debug Player installer keeps giving the same message.
Does anybody knwo how I can install the Flash Debug Player in IE10?

I do not know, but check if there is anything useful in http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flas h_player_windows8_admin_guide.pdf

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!

Linux Debugger and Debug Player

Similar Messages

Maybe you are looking for