DL Break Point - Problem/Question

Recently I've been getting some complaints from my customers that there DVD starts to Pixelize / Break-up on the point the DVD switches layers. Some people even claim the DVD stops all together at the break point.
Not all of the DVD - 9's I sell do this. But it does seem like the complaints have increased.
Is this a problem with my Software (DVDSP 3) or the Replicator im using?
I master all the DVD's on DLT, and than send those to the Replicator. I also chose my own breakpoint.
Could it maybe be the brand of the DVD player having trouble reading the switch? I've asked that they send the problem DVD back to me and it plays fine on my Sony DVD Player.
Anyone else have problems with DVD 9's?
Thanks,
Mike A.

Eric,
You should not be saying that DVD SP is not a good pre-mastering tool, like you're saying here, and have been saying on boards elsewhere over the last period.
It's not true. Actually, the exact opposite is true - tests show DVD Studio Pro has the best pre-mastering formatter on the market; MUCH better than Scenarist and Creator, Encore, and even the vaunted Toshiba DVD Authoring system. And yes, better than even DVDAfterEdit Mastering Edition.
Just run any of the above formatters' DDP output through EclipseSuite 5.0, like I have, and look at all the UDF errors you'll find in all of them - except DVD Studio Pro's output; it's the cleanest.
Maybe what you meant is that ALL authoring systems can hand you your you-know-what in a can, if you don't watch it. That's true.
When I pre-master for a studio running DVD SP, I ALWAYS have the good folks send me a DDP Image on hard drive. And if I'm not adjusting the Image with DVDAfterEdit, I'll format their DVD SP DDP Image straight to tape (after extracting the VIDEO_TS folder for rounds of tests including the DVD Forum's MEI DVD-Video Verifier, and even burn a disc from it for player bank testing).
True, their are at times something wrong with the DVD SP DDP Image that I find with the EclipseSuite; allot of these warnings and errors have to do with project settings (true, some of them shouldn't be there or initially set that way). But if you know what you're doing, and have some guidance when needed (which I provide my clients), then most of the time DVD SP will come through, beautifully.
Since, DVD SP 2.0 when the new Spruce Maestro code set was introduced, things vastly improved. When was that, 4 years ago? Now, I find DVD SP very reliable, with most of the mistakes coming in the authoring and/or how the project was first submitted, before it came to me.
So anyway, please, keep to the facts in the future.
Thanks,
Trai
Trai Forrester
TFDVD Research Labs
<edited by host>

Similar Messages

Bitrate and break point problems

Hello All,
I am trying to create a dual layer dvd containing 37 chapters (all average 3 min. a piece) and 2 audio tracks (one with commentary) with DVD studio Pro 3. On my first build, the disc meter was 7.6 GB large. On a dual layer this should fit with no problems, right? The build got to muxing and cancelled saying "the video bitrate is too high". I read somewhere on these posts that this doesn't matter too much if you're planning on burning to Toast, which is what I was going to do. So I tried formatting and I keep getting the "can't find a suitable break point error". I then tried making several of the chapter markers break points but it didn't like any of them and I still keep getting the same error message on formatting. Any help is greatly appreciated!

Carson:
Wellcome to the forum!
High bitrate
First at all, you probably are using AIFF audio (uncompressed). If that's the case encode your audio to Dolby 2.0 (AC·) and you'll get a lower total bitrate and more free space.
You must look for A.Pack app in your applications folder to encode to AC3. You can take a look to this tutorial about Encoding AC3 with A.Pack (from KenStone site).
You didn't mention your MPEG2 encoding settings, did you used any standard Compressor preset?
37 chapters x 3 min means less than 120 minutes. Encoding your audio to AC3 and using the 120 Min Compressor preset will let you fit your project in a DVD5.
Hope it helps !
Alberto

Dual Layer Break Point problem

Hi,
I just found out after I updated DSP 4 to version 4.0.3 my Layer 1 on every project since updating gets corrupted!
I thought it was the Dual Layer discs I used that caused the problem, but after I re-installed DVD Studio to the original version 4.0.0 the same project worked perfect.
Anyone else have issues with Dual Layer Break Point after updating to 4.0.3?
I have tried different chapters as layerbreak points on my project, and even a test project, with the same result. The finished discs is barely playable on some DVD players, showing wierd interference and noise, and DVD Player on mac crashes when reaching the dual layer break point, and the plant i send the master have a software to check DVDs and they said that it couldnt find/was corrupt Layer 1 on one of my discs. Hope someone can fix this, DSP is the best software otherwise!
Best regards,
Mats.

DVD+R or DVD-R?
http://documentation.apple.com/en/dvdstudiopro/usermanual/index.html#chapter=1%2 6section=9%26tasks=true
DVD+R Double-Layer
You can use DVD+R double-layer media, often referred to as DVD+R DL, for burning your dual-layer projects. With DVD+R double-layer media, DVD Studio Pro places the layer break point and sets the switch point to be nonseamless as specified in your project.
DVD+R double-layer discs require you to use the Opposite Track Path (OTP) direction setting when burning the disc. This means that the first layer must be larger than the second layer. See Setting the Dual-Layer Direction for more information.
While DVD+R double-layer discs allow you to burn your dual-layer projects, they tend to have more compatibility issues than the other types of DVD media.
DVD-R Dual-Layer
If your system contains a DVD drive that can write to the new DVD-R dual-layer media, you can burn your DVD project to it with DVD Studio Pro. However, there are several issues:
Because currently DVD Studio Pro has no way to identify DVD-R dual-layer media as having two layers, burning a dual-layer project to it results in the appearance of an alert message telling you that the DVD media may have insufficient room to hold the project. This message is based on the assumption that the disc is single layer. Both layers of the disc will be written to as needed, however, when you click Continue.
If you are burning a dual-layer project, the break point you set will not affect where the layer break actually occurs. Instead, the first layer is written to until filled, at which point the drive switches to writing to the second layer.
The switch between layers is a seamless layer change not supported by some DVD players, which may stop playing the disc when the switch point is reached.
Important: Do not use DVD-R dual-layer media unless these issues do not impact your project.

DVD Studio Pro Dual Layer Break Point Problem

I have a problem with a disc that I am burning. It is a dual layer (the break point is not set to seamless) with 1 movie that is about 3.6 GB and 1hr 23 min long, a 30 min slideshow, another 30 min extra and five other extras that total to about 20 min. I put the dual layer break point at the beginning of the slideshow, everything played fine on the computer, but on the Panasonic DVD player it just freezes at 35 seconds into the slideshow. Its never had a problem with DLs before. Itried the DVD on my softmodded Wii, on a program for it called WiiMC (it uses Mplayer) and everything played fine. I tried another burn where i set the break point to fifteen minutes before the end on the main 1:23 movie and on the DVD player it still froze at 35 seconds on the slideshow. Is there anything that you guys can suggest to help?

DVD+R or DVD-R?
http://documentation.apple.com/en/dvdstudiopro/usermanual/index.html#chapter=1%2 6section=9%26tasks=true
DVD+R Double-Layer
You can use DVD+R double-layer media, often referred to as DVD+R DL, for burning your dual-layer projects. With DVD+R double-layer media, DVD Studio Pro places the layer break point and sets the switch point to be nonseamless as specified in your project.
DVD+R double-layer discs require you to use the Opposite Track Path (OTP) direction setting when burning the disc. This means that the first layer must be larger than the second layer. See Setting the Dual-Layer Direction for more information.
While DVD+R double-layer discs allow you to burn your dual-layer projects, they tend to have more compatibility issues than the other types of DVD media.
DVD-R Dual-Layer
If your system contains a DVD drive that can write to the new DVD-R dual-layer media, you can burn your DVD project to it with DVD Studio Pro. However, there are several issues:
Because currently DVD Studio Pro has no way to identify DVD-R dual-layer media as having two layers, burning a dual-layer project to it results in the appearance of an alert message telling you that the DVD media may have insufficient room to hold the project. This message is based on the assumption that the disc is single layer. Both layers of the disc will be written to as needed, however, when you click Continue.
If you are burning a dual-layer project, the break point you set will not affect where the layer break actually occurs. Instead, the first layer is written to until filled, at which point the drive switches to writing to the second layer.
The switch between layers is a seamless layer change not supported by some DVD players, which may stop playing the disc when the switch point is reached.
Important: Do not use DVD-R dual-layer media unless these issues do not impact your project.

Problems with break point in Dual Layer project

Hi,
I'm currently having a problem setting a break point in a Dual Layer DVD project in DVD Studio Pro 4. I have a project that has 5.9 GB of data (5 shows with between 7-8 chapters in each). The problem I'm having is that in the 5th chapter of the 4th show, there is a freeze frame hickup when I burn the disk. I've tried moving around the chapter mark, deleting them and re-adding them, re-exporting the media (it is in MPEG-2) in all combinations of those and am still having the freeze problem at that chapter mark. I've gone back to the original media and there are no problems there.
What I think the problem is is that the disk is automatically setting the break point for the dual layer disk at that chapter mark. However, when I go into the project and try to set the break point manually from the dropdown, I can't seem to select anything. The default is the begining of the 5th track, and I can only change it to automatic and back again. Anything else I select just goes back to that 5th track, but I still think it's actually doing automatic instead. I'm using a Verbatim DVD+R DL if that helps anything as well.
To all, do you agree that the problem is most likely due to the break point? And if so, how do I change the break point to the beginning of either the 3rd or 4th of the shows instead of having it seem to be stuck on automatic?
Thanks in advance,
Chris

Alright, to answer my own question. Here's what I think the problem was.
There are actually two Disk/Volume menus: one in the Disk settings when you're actually working in the project and another when you go to build and format. I kept trying to set the break point in the first one--in the disk settings in the project--and it wouldn't let me because it can only be set when building and formatting.
It's kind of an annoying settup that there are two identical menus that don't fully communicate with each other, but in the end the solution has been solved.
Chris

Problem setting External break point..

Hi All,
I am using EP6 SP14 and R/3 4.6C. Java Webdynpro aRFCs to connect to R/3 BAPIs. I am having problems setting up external break points. I don't see Debug option in "Utilities -> Settings -> ABAP Editor". Do we have this option in R/3 4.6C? If yes how to enable the option? If no, what is the work around to debug the BAPI through Portal.
Helpful answers will be rewarded.
Regards,
Uday.

Hi,
Pl go through this
Debugging ABAP Code from within Web Dynpro Application
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0e9a9d90-0201-0010-478e-991dbea73a30
It explains step by step process
Regards
Ayyapparaj

Forte for JAVA: Problems with break points

Dear all,
I have the following problem:
When setting breaks point within the code of my web application (servlets and JSP) the debugger does not seem to be able to find them and to stop where I would it to :o(
When approching a portion of code that I know have a break point, I get the following message in the debugger window->
Connecting to localhost.localdomain:11555
Connection established
Breakpoint reached at line ? in class org.corproware.strutsrelated.listener.DBPoolListener by thread main.
Note the interrogation mark (?) instead of a valid line number.
It looks like I have the same poroblem with a simple java "HelloWorld"
Is their something I don't get or is it a known problem?
Many thanks!

Sorry mate, wrong forum. You shoud try Sun ONE Studio Forum isntead of this one. It is for UDS (Formerly known as Forte)

Problems With Dual Layers Break Points

I have 3 G5 Macs all without intell chip sets. I have tried this with all 3 Macs so lets take the newest one of the 3. Its running on mac osx version 10.4.11 Processer and is 4x2.5 ghz power pc g5 with hl-dt-st dvd-rw gwa-416sb. I can burn single DVD'S all day long, but the problem starts with dual layers. I am using verbatim DVD+R DL. I have one movie which is 2 hours and 36 minutes it burns fine when I burn a single layer, however when I try to build and format a dual layer I get that message window: formatting failed (its says formatting was not successful, the image exceeds the max allowed size for a dual layer configuration.) That is on automatic breakpoint. I have tried inputting in my own break point no matter where I put it the same message window appears. I am using DVD SP 4.1.2 also on FCP 5.1.4. I also tried buring dual layers on Sony DRX A10 UL-T all was working fine last year. I cant figure out why this has changed. Any suggestions will be helpful and appreciated. Sincerely Bob.

Welcome to the boards
Since you are using a Dual Layer Disc, there has to be a break point where it crosses over from Layer 0 to Layer 1, if you have no Chapter Markers at all (or a limited number of Markers, none of which fall near the point which is a bit more than half the size of the assets you will get an error that a Layer is the wrong size.
What you do is
1.) Set up markers in the areas where your would guesstimate the Layer Break(s) should be
2.) Build the project (but not format)
3.) Format a Disc (in the dialog that comes up, click on advanced tab, then where it says break point, use the pulldown which will have all valid breakpoint markers dark/black, while non-valid Layer Break Markers will be faded) If no marker is black there is no marker in the right place, regardless of you use automatic or not.
If the message is not for a layer issue as above (meaning one of the two layers exceeds the permissable size) then it can be an encoding rate issue. 2 Hours and 36 Minutes on a DL should be about 6.9 Average with AC3 audio @ 192. Even then it may be too close depending on menus and the rest. If using uncompressed audio or higher settings for video, could be the problem.
http://dvdstepbystep.com/faqs_7.php

Problem chosing layer break point for multi-movie DL DVD

HI. If you're authoring a DL DVD containing several short movies which can be selected from a menu in any order, how are you supposed to know which order they're burnt to disc in so as to know where the layer break point needs to be? Is media burnt in the order it's added to the project or what? Does it actually matter about choosing a LBP manually so long as DVDSP provides a choice of automatically determined points?

You can use VTS view to see the order they are laid out in
http://dvdstepbystep.com/vts.php
As to manually selecting a layer break, you can if you want to, especially if you know a section is a fade to black (for instance) where it will be less noticeable.
Some background -
There has to be a break point where it crosses over from Layer 0 to Layer 1, if you have no Chapter Markers at all (or a limited number of Markers, none of which fall near the point which is a bit more than half the size of the assets you will get an error that a Layer is the wrong size.
What you do is
1.) Set up markers in the areas where your would guesstimate the Layer Break(s) should be
2.) Build the project (but not format)
3.) Format a Disc (in the dialog that comes up, click on advanced tab, then where it says break point, use the pulldown which will have all valid breakpoint markers dark/black, while non-valid Layer Break Markers will be faded) If no marker is black there is no marker in the right place, regardless of you use automatic or not.
4.) If the layer break(s) are not where you would like them (in other words a place where they may be more noticable) use VTS view to re-order then go back to step 1.
When you do enough DLs, you start getting a sense based on the size of tracks where things should land

Break point in smart form

Dear Gurus....
I am new to smartforms. I have a report which is to be integrated with smart form. I want each PO should start from a new page. I have tried putting an alternative and command in main window but it doesnot solve my problem. Please help me out as i need the solution very urgently...
please mail me the solution here or to my mail id [email protected]
Thanks in advance.

Hi Ajay,
If your question is regarding break point, then create a program line node before the alternative condition and code "break-point". Next time when you execute the program it will stop at this point.
Please let me know what are you displaying in the form. I understand that you want to have a page break for each PO. Are using Table node?
Thanks
Vinod

Dual layer DVD, help with break point

after reading alot of the previous posts on setting a dual layer break point, it seems the best way is to find the general area of where one thinks the break should be and then put in several markers in that area. My question is what type of markers to put in (ie. chapter, button highlights, dual layer break point)? Should i be able to put more than one Dual Layer break point? DVDSP is only allowing me to set ONE Layer Break Point out of the several points that i put in the area i think that the layer break should be, am i doing something wrong? Also, to avoid this whole trial and error process, can i simply do my "build" without any markers/break points and then burn the VIDEO_TS folder in Toast and let Toast find the break point? By the way, this disk will be replicated in case anyone forsees any problems with Eclipse, thanks for any help!

If after building only one marker is black (not gray) it is the only legit marker and why it is limited. The layer break will be on the DLT where it is set
I had one project that took quite awhile to find a place to put the marker to get a legal DL break point
http://discussions.apple.com/thread.jspa?messageID=4032103&#4032103

Break points and watch points

Hi all
 Can anybody help me using break points and watch points.what do they exactly do as well..
Thanks
abap user

Hi
Breakpoints
Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more 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.
Breakpoint
at statement The Debugger stops the program directly before the specified statement is executed.
Breakpoint 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.
Use
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. 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 (for example, only activate the breakpoint after it has been reached five times).
Special Dynamic Breakpoints
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 program 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.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
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:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
2. 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:
1. Position the cursor on the line in which you want to set the breakpoint.
2. 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.

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...
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:
1. Choose Breakpoint  Breakpoint at  Event/Subroutine.
2. 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.
3. 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:
1. Choose Breakpoint  Breakpoint at  Function module...
2. 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.
3. 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 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.
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.
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.
 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.
 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.
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:
1. Choose Breakpoint  Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears.
2. Decide whether you want to set a local or global watchpoint.
3. 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.
4. 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 .
5. 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
6.
7. 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.
To create a logical link between watchpoints:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to open the watchpoint display.
2. Set the Logical operator between watchpoints option.
The default value is always OR .
Changing Watchpoints
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the pencil icon in the line containing the watchpoint you want to change.
3. Change the watchpoint attributes in the Create/Change Watchpoint.
3. Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint  Delete or Breakpoint  Deactivate/activate. Instead, proceed as follows:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. 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.
Reward ifusefull

Break Points while remote debugging not working in Eclipse

I have set up my tomcat to listen for debugger connections on the default pot 8000. Now when I set break points in the code, it does not show the execution stop at that particular line.
Now why would that be? Am I missing somethiing?
I have built the files with debugging on.
thanks
M

http://kaustavdm.in/2014/08/connect-firefox-os-spreadtrum-device-adb.html
check this out, it should fix all your problems !

Dump while setting a break point in ECC 6.0

Dear Experts,
In ECC 6.0, when I try to put a break point in the program to stop the control there. I am not able to do so, it is going to dump. The dump message is also not very clear. Do anyone of you are facing the same problem. Any idea why is this happening and how do I fix it.
Can it be due to the improper installation? Please respond.

First of all thanks to Mickey, Nitin, Anki, Sujit, Red, Madhu, Vibin for the quick response...To be honest I did not expect such a response as a new member to the SDN community...I am sorry I could not mention the detail about the dump initially...Here is the detailed description..
Issue: In ECC 6.0, when I write a simple ABAP program (e.g. 'Hello World' program). When I try to keep the cursor on any abap statement and click on the 'session break point' icon in the tool bar to set the break point, i get a status message 'Compling SAPLBREA in separate task and finally i get the dump.
Dump Detail :
Runtime Errors: DBIF_REPO_SQL_ERROR
Short Text : SQL error 1115 occurred when accessing program 'LNAVIDAT' part "SRC".
Program: SAPLBREA
Include: LBREATOP
Row: 41
There is a an include being called at line no 41, which is "Include LNAVIDAT".
Now when I click on the 'debugger' icon in the dump...It points to a functional module "RS_SET_BREAKPOINT"
Also, while double clicking on this include to see the code within, it issues an error message saying "SQL error occurred when accessing the table TRDIR".
Or
While trying to display the code of the include LNAVIDAT in se38 to see what is wrong with that i get another dump and this time it points to be SELECT query in the dump which is:
SELECT SINGLE * from PROGDIR WHERE name = rs38m-programm
and state = active.
Thereafter, i keep getting dumps when i try to go to any T.codes (e.g. se11, se38 etc.). until i log off and log in again. Hope this helps you guys understanding the problem. Being new to SAP, I have no clue why is this happening and how to fix it. Thanks in Advance.

Break Point in Webdynpro JAVA and SAP

Good Morning.
I am creating a development for web dynpro Java using Function Module RFC in ABAP.
I want know how can put a break point in the system SAP ERP (Backend) and run an application in web dynpro java?
I did this steps:
1.) SE37--->name RFC
2) button Display
3) Set/Delete external Break point.
4) In the SAP Netweaver Developer Studio >Name of project>Webdynpro>Applications>Name Appplication-->deploy new archive and run.
But this not stop.
The question is :
How can do this?
Kind Regards

Hi,
Refer this article: [Debugging ABAP Code from within Web Dynpro Application|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/0e9a9d90-0201-0010-478e-991dbea73a30&overridelayout=true].
I hope it helps.
Regards
Arjun

DL Break Point - Problem/Question

Similar Messages

Maybe you are looking for