Debugger and smart data

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

Similar Messages

  • Problem displaying data and Smart data debugging pl/sql

    I'm using JDev 9.0.5.1 build 1065, when i debug a PL/SQL function from the connections navigator, it allows me to stop at a breakpoint, but it doesn't display anything in the data or smart data panes. Do i need to change a config setting somewhere ? The PL/SQL is in an Oracle 8i database, does it need to be 10g for this functionality to work ?
    Thanks
    Alistair

    Are you trying to debug ASP.NET or a windows app or direct debugging?
    If a windows app or direct debugging, follow these steps:
    http://cshay.blogspot.com/2006/07/plsql-debugger-in-visual-studio.html
    If ASP.NET, follow part of the steps above to configure, but then use these steps for External App debugging:
    Debugging PL/SQL from .Net 2003

  • Smart data value display ? BUG sqldeveloper EA2 but works in plsqldeveloper

    Hi,
    The below mentioned debug facility works in plsqldevloper but the same does not work in sqldeveloper both on 10g and 11g Oracle Database
    Has anyone enocuntered this bug as smart data value / tooltip not displayed in sub proc while debug in
    sqldeveloper 3.0.02
    tooltip and values are dispalyed during debug in v_var1 but as u debug further to (sub procedure within the main procedure code) i.e procedure test1 ,values of v_var2 not being displayed in tool tip / smart data value until the debugger cursor comes out the sub procedure . Kindly replicate the example shown below in sqldevloper EA2
    create or replace
    PROCEDURE PROCEDURE1 AS
    v_var1 char(20);
    v_var2 char(20);
    v_var3 char(20);
    procedure test1 is
    begin
    v_var2 := 'this is sub proc' ;
    end test1;
    BEGIN
    v_var1 := 'this is a test';
    test1;
    END PROCEDURE1;
    Any comments/solution will be appreciated
    SS
    Edited by: user575518 on Jan 17, 2011 11:20 PM
    Edited by: user575518 on Jan 19, 2011 9:45 PM

    Hi,
    The below mentioned debug facility works in plsqldevloper but the same does not work in sqldeveloper both on 10g and 11g Oracle Database
    Has anyone enocuntered this bug as smart data value / tooltip not displayed in sub proc while debug in
    sqldeveloper 3.0.02
    tooltip and values are dispalyed during debug in v_var1 but as u debug further to (sub procedure within the main procedure code) i.e procedure test1 ,values of v_var2 not being displayed in tool tip / smart data value until the debugger cursor comes out the sub procedure . Kindly replicate the example shown below in sqldevloper EA2
    create or replace
    PROCEDURE PROCEDURE1 AS
    v_var1 char(20);
    v_var2 char(20);
    v_var3 char(20);
    procedure test1 is
    begin
    v_var2 := 'this is sub proc' ;
    end test1;
    BEGIN
    v_var1 := 'this is a test';
    test1;
    END PROCEDURE1;
    Any comments/solution will be appreciated
    SS
    Edited by: user575518 on Jan 17, 2011 11:20 PM
    Edited by: user575518 on Jan 19, 2011 9:45 PM

  • Debugger and Citrix

    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

  • Smart data

    Hi,
    Probably not a very smart question, but I'm figuring out how the debugger works and wonder why smart data are smart. What can you do with smart data that you can't do with 'normal' data (on the data tab)?
    Thanks for any tip

    Don't worry, I think everyone else is asking themself the same thing.
    And at least for me, the contents are always blank.
    I guess this is a non or bad implemented leftover from what got copied from the JDeveloper framework.
    In theory it should only be showing contextual data, rather than everything available, but it doesn't bother me.
    Regards,
    K.

  • What is the diff b/w Sap Scripts and Smart Forms

    Hi,
          Whats the diff b/w SAP Scripts and Smart Forms..
             I need the internal explanation for both Smart Forms and SAP Scripts mean when we execute what happens whether Print Program r Forms starts execution 1st  and SIMILARLY FOR SMARTFORMS WHETHER FM'S  R FORMS.
    Thanks & Regards,
    Gopi.

    Hi
    Difference with SMARTFORMS vs. SapScript(SE71)
    The Following are the differences :-
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Labels cannot be created in smartforms.
    d) Routines can be written in smartforms tool.
    e) Smartforms generates a function module when activated.
    f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
    It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.
    In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
    In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
    For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
    g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
    check out this link:
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    Reward points if helpful.
    Regards,
    Swathi.

  • How to add a new metadata field to iPhoto where new field is calculated as age in years and month based on a specific date and the date photo was taken ? I want to calculate and display the age of my two kids on every photo.

    Hi
    How can I add 2 new metadata-fields to every photo in iPhoto ?
    The new fields should state the age of my kids in years and months based on the date that they were born and the date that photo is taken.
    Exampel:
    My son is born 01.01.2010
    My daughter is born 01.01.2012
    Photo taken by data
    Aage of son
    Aage of daughter
    01.07.2011
    1 year 6 month
    not born yet
    01.01.2014
    4 year 0 month
    2 year 0 month
    I would like to be able to search by kids age and get the info displayed when doing slideshows.
    How to do this in iPhoto ?
    Any alternatives to accomplish the same ?
    Kind regards

    It can't be done with iPhoto.  There are some DAM (digital asset management) applications that can write to other IPTC fields that iPhoto can't read. One such app is Media Pro 1.
    However you would have to calculate the age for each date and add it to one of the fields. There are online age calculators that can do that for you: Age Calculators
    If you go thru that much trouble then use iPhoto, make the calculations and add the age to the Description field.  Then you can use Smart Albums to search for 1year 6 month text.
    OT

  • Follow up question about interpreting smart data test on 160GB classic

    I posted this question regarding the problem I am having with my 160GB ipod classic:
    http://discussions.apple.com/thread.jspa?threadID=2153948&tstart=0
    It appears noone is able to help me, so I have found some more information:
    In short, itunes will not write to my 160GB ipod once it reaches about 35GB / 160. Windows will write to it, but only at 500KB/sec rather than the usual 19+Mb/sec. It just crawls once it hits that point. After following some advice online I came up with the following results using the HD tests in diagnostic mode.
    smart data test:
    retracts: 138
    rallocs: 563
    pending sector: 55
    poweron hours: 1016
    starts/stops: 267
    temp: current 26C
    temp: min 19C
    temp: max 53C
    and for the HDD spec test:
    sno: (not sure if i should post a serial number?)
    FW Revision: NB100-05
    LBAs: 0x12a19eb0
    These are the only tests that show up under the I/O HardDrive section. Should there be more? It seems like there might be from what I read, but I am not sure.
    Anyway, any help interpreting these results would be greatly appreciated.

    adame wrote:
    rallocs: 563
    pending sector: 55
    etc.
    Your drive is probably toast. Compare your SmartData stats with mine:
    Retracts: 844
    *Reallocs: 12*
    *Pending Sectors: 0*
    PowerOn Hours: 2037
    Starts/Stops: 830
    Temp: Current 29c
    Temp: Min 10c
    Temp: Max 50C
    I've only 12 remapped sectors and none pending. From the Wikipedia S.M.A.R.T. article:
    *Reallocated Sectors Count*
    Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks this sector as "reallocated" and transfers data to a special reserved area (spare area). This process is also known as remapping, and "reallocated" sectors are called remaps. This is why, on modern hard disks, "bad blocks" cannot be found while testing the surface – all bad blocks are hidden in reallocated sectors. However, as the number of reallocated sectors increases, the read/write speed tends to decrease. The raw value normally represents a count of the number of bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate.
    *Pending sector count*
    Number of "unstable" sectors (waiting to be remapped, because of read errors). If an unstable sector is subsequently written or read successfully, this value is decreased and the sector is not remapped. Read errors on a sector will not remap the sector (since it might be readable later); instead, the drive firmware remembers that the sector needs to be remapped, and remaps it the next time it's written.
    I'm sure you'll find the counts go up if you try to do a surface scanning disk check. Sorry it's not better news but at least you know where the problem lies. Assuming your iPod is out of warranty it's probably time to get your iPod refurbished with a new drive or to buy a new iPod.
    tt2

  • Characters such as apostrophes and smart quotes turning into boxes or question marks

    We recently upgraded from CF5 to CF7 and are having a problem
    with previously saved text that no longer displays correctly. Some
    characters (apparently, non-ASCII characters such as curly
    apostrophes and smart quotes) are rendering as boxes or question
    marks. We recently upgraded to Oracle 10g from Oracle 8i, but this
    problem appears to be independent of the database that the text is
    stored in. Here is sample code that will illustrate the problem:
    <CFSET string1="Department’s">
    <CFSET string2="hey—there">
    <CFOUTPUT>
    string1 is #string1#
    <BR>
    string2 is #string2#
    </CFOUTPUT>
    output looks like this:
    string1 is Department?s
    string2 is hey?there
    These are rendered as boxes when viewed in Internet Explorer.
    (They show up as question marks when I copy and paste them here.)
    The Demoronize UDF helps *some* of the time, but this is
    still happening with a lot of text, especially text that gets
    pasted from a website into a form, then saved to a database. Does
    anybody have a solution for this? This is breaking my applications
    and is incredibly annoying. I'd like to either replace the
    problematic characters at the time they are displayed, or replace
    them when they are input in the database in the first place (and go
    back and update all the previously saved data to replace the
    problematic characters with plain text equivalents).
    Any suggestions appreciated.

    I finally isolated the problematic characters so I edited the
    DeMoronize UDF (available at cflib.org) by adding the following
    text replacements at the bottom:
    text = Replace(text, chr(8208), "-", "ALL");
    text = Replace(text, chr(8209), "-", "ALL");
    text = Replace(text, chr(8210), "&ndash;", "ALL");
    text = Replace(text, chr(8211), "&ndash;", "ALL");
    text = Replace(text, chr(8212), "&mdash;", "ALL");
    text = Replace(text, chr(8213), "&mdash;", "ALL");
    text = Replace(text, chr(8214), "||", "ALL");
    text = Replace(text, chr(8215), "_", "ALL");
    text = Replace(text, chr(8216), "&lsquo;", "ALL");
    text = Replace(text, chr(8217), "&rsquo;", "ALL");
    text = Replace(text, chr(8218), ",", "ALL");
    text = Replace(text, chr(8219), "'", "ALL");
    text = Replace(text, chr(8220), "&ldquo;", "ALL");
    text = Replace(text, chr(8221), "&rdquo;", "ALL");
    text = Replace(text, chr(8222), """", "ALL");
    text = Replace(text, chr(8223), """", "ALL");
    text = Replace(text, chr(8226), "&middot;", "ALL");
    text = Replace(text, chr(8227), "&gt;", "ALL");
    text = Replace(text, chr(8228), ".", "ALL");
    text = Replace(text, chr(8229), "..", "ALL");
    text = Replace(text, chr(8230), "...", "ALL");
    text = Replace(text, chr(8231), "&middot;",
    "ALL");

  • What is my best option for a family plan. We have 1 smartphone that uses very little data a usually wifi is avaiable and 3 basic phones. Currently we have 700 shared minutes and unlimited texting. And 30 data. I don't think he needs that much as wifi is e

    What is the best family plan option. Currently have one smart phone with 30gb of data and 3 basic phones. Also have home phone for $20/month. Current plan is 700 shared minutes and unlimited texting. My bill is close to $200/month, looking to lower if possible.

    On a tablet- pse forgive typos....
    Great Advice given earlier by SuzyQ   - I believe the question not asked of you is ---what do you want to pay for the services that you need.  I think that it would narrow the groups suggestions if you could narrow your needs.
    For example: I need talk and text on 4 phones and some data say, 2 Gig, on only one of the phones. what plan is the best cost for me? You may also need to ask what the cost may be to switch to a different plan. I suspect that there will be no cost within Verizon-but ask anyway.
    I do not think that you can have a smart phone on any Verizon plan unless you agree to buy data for that phone. Also, you said that wifi is often available-however, I do not believe that Verizon allows talking over wifi without consuming airtime minutes-only data over wifi avoids your allowance to be impacted.
    As most here already know, several other service providers offer wifi-friendly service (talk/text/data) that will provide  home/business/restaurant service without impacting your allowance- just not here.
    After getting some suggestions here, call 611 and confirm availibility and price.    
    Best of luck in your research.

  • SSD freezes for a few days then returns to normal and smart OK

    Hello
    <EDIT>
    The freezes have stopped as suddenly as they had started. Logs show all that all smart tests passed successfully for the last three days:
    # journalctl |grep self-test
    juil. 26 05:05:25 llewellyn smartd[442]: Device: /dev/sdb [SAT], previous self-test completed without error
    juil. 28 02:41:32 llewellyn smartd[459]: Device: /dev/sda [SAT], previous self-test completed without error [x3]
    juil. 29 02:41:32 llewellyn smartd[459]: Device: /dev/sda [SAT], previous self-test completed without error [x3]
    Do you mind to share your interpretation of this behavior? Call me dumb but was this SSD getting tired of fasting (Ramadan ended yesterday) or has a strong personality... :-o ?
    In the meantime have increased backups frequency.
    </EDIT>
    My system started to freeze from time to time with the error log below. But SMARTctl says drive's fine. Already happened six months ago then the problem vanished. Wonder how to effectively check a SSD's status?!
    This workstation has two Sata Hard Drives and a SanDisk SDSSDX120GG25 15 months old.
    Kernel~3.15.5-2-ck x86_64 Up~6 days Mem~1533.7/3770.6MB HDD~940.2GB(51.1% used).
    1) smartctl (and hdsentinel) says drive's fine:
    # smartctl -a /dev/sda
    smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.15.5-2-ck] (local build)
    Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: SandForce Driven SSDs
    Device Model: SanDisk SDSSDX120GG25
    Serial Number: 120645400154
    LU WWN Device Id: 5 001b44 7229bb25a
    Firmware Version: R211
    User Capacity: 120 034 123 776 bytes [120 GB]
    Sector Size: 512 bytes logical/physical
    Rotation Rate: Solid State Device
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Wed Jul 23 11:23:05 2014 CEST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x02) Offline data collection activity
    was completed without error.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    # smartctl -A /dev/sda
    smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.15.5-2-ck] (local build)
    Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF READ SMART DATA SECTION ===
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 110 110 050 Pre-fail Always - 0/29297014
    5 Retired_Block_Count 0x0033 100 100 003 Pre-fail Always - 0
    9 Power_On_Hours_and_Msec 0x0032 088 088 000 Old_age Always - 11290h+19m+12.600s
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 180
    171 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0
    172 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0
    174 Unexpect_Power_Loss_Ct 0x0030 000 000 000 Old_age Offline - 66
    177 Wear_Range_Delta 0x0000 000 000 000 Old_age Offline - 5
    181 Program_Fail_Count 0x0032 000 000 000 Old_age Always - 0
    182 Erase_Fail_Count 0x0032 000 000 000 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    194 Temperature_Celsius 0x0022 032 035 000 Old_age Always - 32 (Min/Max 12/35)
    195 ECC_Uncorr_Error_Count 0x001c 120 120 000 Old_age Offline - 0/29297014
    196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0
    201 Unc_Soft_Read_Err_Rate 0x001c 120 120 000 Old_age Offline - 0/29297014
    204 Soft_ECC_Correct_Rate 0x001c 120 120 000 Old_age Offline - 0/29297014
    230 Life_Curve_Status 0x0013 100 100 000 Pre-fail Always - 100
    231 SSD_Life_Left 0x0013 100 100 010 Pre-fail Always - 0
    233 SandForce_Internal 0x0000 000 000 000 Old_age Offline - 6048
    234 SandForce_Internal 0x0032 000 000 000 Old_age Always - 11062
    241 Lifetime_Writes_GiB 0x0032 000 000 000 Old_age Always - 11062
    242 Lifetime_Reads_GiB 0x0032 000 000 000 Old_age Always - 3152
    2) the system freezes (for about 40 seconds) in what appears to be random, for 4 days:
    $ dmesg
    [511666.153499] ata1: EH complete
    [511666.153512] EXT4-fs (dm-3): discard request in group:1055 block:7424 count:65 failed with -5
    [511827.786342] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x6 frozen
    [511827.786347] ata1: SError: { PHYRdyChg CommWake }
    [511827.786350] ata1.00: failed command: DATA SET MANAGEMENT
    [511827.786354] ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 4 dma 512 out
    res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [511827.786357] ata1.00: status: { DRDY }
    [511827.786360] ata1: hard resetting link
    [511828.091280] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [511828.102562] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    [511828.102568] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    [511828.102571] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    [511828.122516] ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
    [511828.122521] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
    [511828.122525] ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
    [511828.132926] ata1.00: configured for UDMA/133
    [511828.133329] ata1.00: device reported invalid CHS sector 0
    [511828.133341] sd 0:0:0:0: [sda]
    [511828.133342] Result: hostbyte=0x00 driverbyte=0x08
    [511828.133344] sd 0:0:0:0: [sda]
    [511828.133345] Sense Key : 0xb [current] [descriptor]
    [511828.133348] Descriptor sense data with sense descriptors (in hex):
    [511828.133349] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [511828.133356] 00 00 00 00
    [511828.133359] sd 0:0:0:0: [sda]
    [511828.133360] ASC=0x0 ASCQ=0x0
    [511828.133362] sd 0:0:0:0: [sda] CDB:
    [511828.133363] cdb[0]=0x93: 93 08 00 00 00 00 04 2e 24 c2 00 00 00 40 00 00
    [511828.133372] end_request: I/O error, dev sda, sector 70132930
    [511828.133389] EXT4-fs (dm-3): discard request in group:1055 block:3680 count:32 failed with -5
    [511828.133390] ata1: EH complete
    # journalctl -xb | grep sda
    juil. 17 11:25:29 llewellyn smartd[451]: Device: /dev/sda [SAT], SanDisk SDSSDX120GG25, S/N:120645400154, WWN:5-001b44-7229bb25a, FW:R211, 120 GB
    juil. 18 00:25:31 llewellyn smartd[451]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 108 to 109
    juil. 19 02:25:31 llewellyn smartd[451]: Device: /dev/sda [SAT], starting scheduled Short Self-Test.
    juil. 19 02:55:31 llewellyn smartd[451]: Device: /dev/sda [SAT], previous self-test completed without error
    juil. 19 03:26:02 llewellyn smartd[451]: Device: /dev/sda [SAT], starting scheduled Long Self-Test.
    juil. 19 03:55:31 llewellyn smartd[451]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34
    juil. 19 03:55:31 llewellyn smartd[451]: Device: /dev/sda [SAT], previous self-test could not complete due to a fatal or unknown error
    juil. 19 11:23:09 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 19 11:23:09 llewellyn kernel: end_request: I/O error, dev sda, sector 72829890
    juil. 19 18:55:15 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 19 18:55:15 llewellyn kernel: end_request: I/O error, dev sda, sector 71426050
    juil. 19 22:14:50 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 19 22:14:50 llewellyn kernel: end_request: I/O error, dev sda, sector 72564994
    juil. 19 23:19:04 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 19 23:19:04 llewellyn kernel: end_request: I/O error, dev sda, sector 56920066
    juil. 20 03:51:16 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 20 03:51:16 llewellyn kernel: end_request: I/O error, dev sda, sector 61002754
    juil. 20 11:36:13 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 20 11:36:13 llewellyn kernel: end_request: I/O error, dev sda, sector 56936898
    juil. 21 22:40:37 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 21 22:40:37 llewellyn kernel: end_request: I/O error, dev sda, sector 64332610
    juil. 21 22:40:37 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 21 22:40:37 llewellyn kernel: end_request: I/O error, dev sda, sector 64332610
    juil. 21 22:56:40 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 21 22:56:40 llewellyn kernel: end_request: I/O error, dev sda, sector 64332226
    juil. 23 06:51:20 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 23 06:51:20 llewellyn kernel: end_request: I/O error, dev sda, sector 63981570
    juil. 23 09:33:24 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 23 09:33:24 llewellyn kernel: end_request: I/O error, dev sda, sector 70140418
    juil. 23 09:36:06 llewellyn kernel: sd 0:0:0:0: [sda] CDB:
    juil. 23 09:36:06 llewellyn kernel: end_request: I/O error, dev sda, sector 70132930
    Six months ago I got the same issue. Disappeared after I upgraded one the Sata Drives' firmware (not the SSD's). strange enough.
    Please help me learn how to check the real state of a SSD?. Hard to move on when you dunno if a drive's issue is hardware related
    Useful References I checked but couldn't learn how to check what's causing the system's freeze:
    * checking SMART's statuses or conditions by GrapefruiTgirl
    * Disabling TRIM on the kernel level (Unresolved) The "failed command: DATA SET MANAGEMENT" shows that the kernel hangs while trying to issue a TRIM command
    * http://www.linuxjournal.com/magazine/mo … t?page=0,0
    Last edited by kozaki (2014-07-29 16:47:19)

    What I find strange is that only one on the ten latest (long?) self-tests couldn't complete, all others went fine. Which one to follow is unclear to me:
    juil. 25 02:35:26 llewellyn smartd[442]: Device: /dev/sdc [SAT], previous self-test completed without error ( x6 )
    juil. 26 02:35:25 llewellyn smartd[442]: Device: /dev/sda [SAT], previous self-test could not complete due to a fatal or unknown error
    juil. 26 02:35:25 llewellyn smartd[442]: Device: /dev/sdb [SAT], previous self-test completed without error
    juil. 26 02:35:25 llewellyn smartd[442]: Device: /dev/sdc [SAT], previous self-test completed without error
    juil. 26 03:35:25 llewellyn smartd[442]: Device: /dev/sda [SAT], self-test in progress, 10% remaining
    juil. 26 03:35:25 llewellyn smartd[442]: Device: /dev/sdb [SAT], self-test in progress, 70% remaining
    juil. 26 03:35:25 llewellyn smartd[442]: Device: /dev/sdc [SAT], self-test in progress, 60% remaining
    juil. 26 04:05:25 llewellyn smartd[442]: Device: /dev/sda [SAT], previous self-test completed without error
    juil. 26 04:05:25 llewellyn smartd[442]: Device: /dev/sdb [SAT], self-test in progress, 40% remaining
    juil. 26 04:05:25 llewellyn smartd[442]: Device: /dev/sdc [SAT], self-test in progress, 20% remaining
    juil. 26 04:35:25 llewellyn smartd[442]: Device: /dev/sdb [SAT], self-test in progress, 10% remaining
    juil. 26 04:35:26 llewellyn smartd[442]: Device: /dev/sdc [SAT], previous self-test completed without error ( x2 )

  • There should be a way to easly switch between wifi and cellular data

    I think apple should put wifi icon and cellular data icon on the notification bar so we can change between them easily or even closing them both. So other smart phone like Samsung did it from a long time and its really easier way so Apple as the greatest company in the smart phones field should do something for this ..

    Read http://www.apple.com/ios/ios7/features/ and in particular the section on control centre.  Maybe that does it for you but you will have to wait until Sep/Oct for the public release

  • Full format on Arch and map badsectors and smart outputs

    Hi.
    I would like to ask for your help. Recently i've been worried about my two Seagate Barracuda 14 series drives because smart provided by a smartmontools shows "end to end error" that is critical to a hard drive condition. I've been searching over the www for more info but most of them tells that drives with "end to end error" should be immediately returned for an RMA. My drives works well, even with this smart information, wrong parameter. I read that under windows doing a full format will check drive for a bad sector and it there are spare, than they would be remaped.
    I would like to ask for the same thing under linux - how to do a full format to check drive condition, to remove existing bad block/bad sectors when they show up? Doing mkfs.ext4 /dev/sdXY will do the same thinh? Maybe using gparted and do it using gparted gui?
    This is my smart from two drives:
    [firekage@arch_desktop ~]$ sudo smartctl -a /dev/sdj
    [sudo] password for firekage:
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.17.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: Seagate Barracuda 7200.14 (AF)
    Device Model: ST2000DM001-1CH164
    Serial Number: Z1E6H7Q4
    LU WWN Device Id: 5 000c50 06596c809
    Firmware Version: CC27
    User Capacity: 2,000,398,934,016 bytes [2,00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 7200 rpm
    Form Factor: 3.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
    SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Thu Dec 18 13:28:05 2014 CET
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 575) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 213) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x3085) SCT Status supported.
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 112 099 006 Pre-fail Always - 42465392
    3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1064
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1566281
    9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2481
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1054
    183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
    184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    188 Command_Timeout 0x0032 100 099 000 Old_age Always - 0 0 3
    189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2
    190 Airflow_Temperature_Cel 0x0022 066 047 045 Old_age Always - 34 (Min/Max 24/34)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 99
    193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 9263
    194 Temperature_Celsius 0x0022 034 053 000 Old_age Always - 34 (0 18 0 0 0)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 4
    240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 1604h+23m+27.451s
    241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 8044262567
    242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1672497340
    SMART Error Log Version: 1
    ATA Error Count: 1
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 1 occurred at disk power-on lifetime: 562 hours (23 days + 10 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 00 01 ff ff ff 4f 00 12:10:45.194 READ DMA EXT
    25 00 01 00 00 00 40 00 12:10:45.175 READ DMA EXT
    25 00 01 ff ff ff 4f 00 12:10:45.158 READ DMA EXT
    f5 00 00 00 4f c2 40 00 12:10:45.140 SECURITY FREEZE LOCK
    b0 da 00 00 4f c2 40 00 12:10:45.113 SMART RETURN STATUS
    SMART Self-test log structure revision number 1
    No self-tests have been logged. [To run self-tests, use: smartctl -t]
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    [firekage@arch_desktop ~]$
    and the second one:
    [firekage@arch_desktop ~]$ sudo smartctl -a /dev/sdk
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.17.6-1-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family: Seagate Barracuda 7200.14 (AF)
    Device Model: ST2000DM001-1CH164
    Serial Number: W1E1WBW0
    LU WWN Device Id: 5 000c50 05cca200b
    Firmware Version: CC24
    User Capacity: 2,000,398,934,016 bytes [2,00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 7200 rpm
    Form Factor: 3.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS T13/1699-D revision 4
    SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Thu Dec 18 13:28:37 2014 CET
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 584) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 214) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x3085) SCT Status supported.
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 11998592
    3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2349
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 4316601253
    9 Power_On_Hours 0x0032 100 095 000 Old_age Always - 592
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 098 020 Old_age Always - 233
    183 Runtime_Bad_Block 0x0032 093 093 000 Old_age Always - 7
    184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    188 Command_Timeout 0x0032 100 098 000 Old_age Always - 3 3 25
    189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1
    190 Airflow_Temperature_Cel 0x0022 068 042 045 Old_age Always In_the_past 32 (1 80 32 24 0)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 210
    193 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 12687
    194 Temperature_Celsius 0x0022 032 058 000 Old_age Always - 32 (0 16 0 0 0)
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 200 199 000 Old_age Always - 47
    240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 4513h+35m+52.508s
    241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 18705892093
    242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 10912938323
    SMART Error Log Version: 1
    No Errors Logged
    SMART Self-test log structure revision number 1
    No self-tests have been logged. [To run self-tests, use: smartctl -t]
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    [firekage@arch_desktop ~]$
    I have found on www that "end to end error" means that chip on drive is either damaged, or broken and can't work properly when checking data that are being writed, they are not in match with data recived and stored in cache.
    Could somebody help? Thanks.
    In fact, it's just a bad joke from seagate. Two drives, rather new, one with around 2500h and one with only 500h are damaged, and damaged critical according to smart when my older Barracuda 11 has around 25000h and works fine! I don't want to spend fortune to hdd, won't buy red series from WD, won't buy green because i read a lot about broken green series drives...and now Seagate...

    davidm wrote:
    My gut feeling is this is nothing to worry about.  What are the odds that both failed in exactly the same way.
    From reading around it seems Seagate's SMART compatibility is questionable and highly proprietary.  More than likely smartmontools is misreporting things under the circumstances.  Apparently Seagate has an iso you can download and test your drives with that for a more accurate diagnoses.
    Here is their answer:What gave you tthat SMART error? It seems to me the
    Linux diagnostic? Our SMART values are proprietary and do not conform to
    the industrie standard. That is why 3rd party tools cannot correctly
    read our drives.
    To check on the condition of the drive, download Seatools for DOS (it
    boots into Free BSD and works with Linux).
    Here is the download link:
    http://www.seagate.com/ww/v/index.jsp?l … 04090aRCRD
    Seatools for DOS is an ISO image file that is burnt to CD. You boot with
    that CD and run the long test that will examine every sector on that
    drive. If Seatools indicates the drive has a problem, you should
    exchange it (it will generate an error code)."
    http://sourceforge.net/p/smartmontools/ … /24435188/
    It seems the problem is not very rare.
    Yes, they suggested me the same thing on Seagate support but...well...i want to be sure...i just can't belive that seatools is far better than smart reads.

  • Used Relocate Masters to new g-drive. Lost Aperature Library and meta data

    how i crashed aperature
    1.56 aperature
    all updates current
    tiger 10.4.11
    all updates current
    Goal was to move Aperature Library from MBP to g-drive.
    what i did:
    1. "Relocate Master" to g-drive. Success. Aperature still viewed all Files with all Meta Data normally.
    2. Collapsed "Library" in Projects Panel. Did not delete Projects. Did not delete any Photos.
    3. Preferences > Image Management > set new Aperature Library on g-drive.
    4. Uploaded new photos from a Canon and viewed them successfully.
    5. Ejected g-drive correctly.
    what Aperature is not doing now:
    1. no Projects show up.
    2. no Referenced Photos show up.
    3. no Vaults show up. Note: the Vault was originally on MBP, but I foolishly did not set one up on g-drive before moving. I also have a back up Vault on a different g-drive that is, unfortunately, not up to date with all current photos before move.
    4. Aperature Library on g-drive is there but can not open any files in it. [note: item 3 above]
    5. Image files listed in g-drive but won't open in Aperature but do open in Preview or Gimp, etc.
    6. Aperature does not show any Vaults nor does it access Referenced Files.
    *Can you help ?*
    *I guess these would be the questions:*
    1. How can I get the pics from the g-drive back into an Aperature Library with all the previous Meta Data attached to each Version?
    2. How do I get the Aperature Library - I put on the g-drive - to open in Aperature?
    3. If #1 is impossible - I guess I set up a Vault on the g-drive and move what I have from the back up Vault mentioned above.
    *Thanks for any advice !!!*

    If I an not mistaken, I may have read through your pdf's quite a while ago. I am still trying to digest them and then apply them to my needs. If I had known that small projects may be faster and easier to manage than larger ones I would have done my imports quite differently. I chose to use Aperture in the first place to organize and add information to photos. I archive old photos. In particularly from 350th Fighter Group, WWII in the Mediterranean. So one "Project" of mine is =/-5000 images in the form of TIFF scans. I imported all of these into 1 project. Then I started applying metadata and keywwords like crazy. This allowed me to start to sort the photos into categories and find multiple version of the same image. I started making stacks of all the multiples. Then with smart albums and smart web sites I was able to create what might now be smaller projects. Since I gather information from others by sharing these photos on a website, You are able to see the smart websites here.
    http://web.me.com/vizcarraguitars/350thFighter_Group_Blog/350th_FG_Blog/350th_FGBlog.html
    One cool thing is that various images reside in multiple smart webs based on common keyword. But now that I have all this organization, it seems it is time to put all my originals in a similar order via Aperture.
    By the way, my files are reference files unless I make the mistake of importing them without leaving them in there original location.
    I am thinking of starting over with blue folders. But I can't seem to get my head around it.

  • 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:

Maybe you are looking for