Help Pls? Debug a program

please can anyone help me debug.
package untitled9;
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
import java.util.*;
import com.borland.jbcl.control.*;
* Title: Administrator Menu
* Description:
* Copyright: Copyright (c) Chengzhi
* Company: wi2 Software Solution
* @author Chengzhi
* @version 1.0
public class Delete extends JFrame {
JMenuBar jMenuBar1 = new JMenuBar();
JMenu jMenu1 = new JMenu();
JMenu jMenu2 = new JMenu();
JMenu jMenu3 = new JMenu();
JButton jButton1 = new JButton();
JButton jButton2 = new JButton();
JButton jButton3 = new JButton();
JLabel jLabel1 = new JLabel();
JTextField jTextField1 = new JTextField();
JButton jButton4 = new JButton();
JButton jButton5 = new JButton();
JMenu jMenu4 = new JMenu();
JMenu jMenu5 = new JMenu();
public Delete() {
try {
jbInit();
catch(Exception e) {
e.printStackTrace();
private void jbInit() throws Exception {
this.setJMenuBar(jMenuBar1);
this.setTitle("New Vision-Delete");
this.getContentPane().setLayout(null);
jMenu2.setText("Save");
jMenu1.setText("Print");
jMenu3.setText("Window");
ImageIcon Back = new ImageIcon(Frame1.class.getResource("BackButton.jpg"));
jButton1.setIcon(Back);
ImageIcon Exit = new ImageIcon(Frame1.class.getResource("ExitButton.jpg"));
jButton2.setIcon(Exit);
ImageIcon Main = new ImageIcon(Frame1.class.getResource("MainButton.jpg"));
jButton3.setIcon(Main);
jButton1.setBorderPainted(false);
jButton1.setBounds(new Rectangle(16, 48, 76, 68));
jButton1.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(ActionEvent e) {
jButton1_actionPerformed(e);
jButton2.setBorderPainted(false);
jButton2.setBounds(new Rectangle(107, 46, 70, 71));
jButton2.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(ActionEvent e) {
jButton2_actionPerformed(e);
jButton3.setBorderPainted(false);
jButton3.setBounds(new Rectangle(189, 47, 78, 69));
jLabel1.setFont(new java.awt.Font("Dialog", 0, 15));
jLabel1.setForeground(Color.blue);
jLabel1.setText("Enter Disc ID:");
jLabel1.setBounds(new Rectangle(11, 140, 285, 37));
jTextField1.setText("665498231");
jTextField1.setBounds(new Rectangle(11, 173, 349, 32));
jTextField1.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(ActionEvent e) {
jTextField1_actionPerformed(e);
jButton4.setText("Ok");
jButton4.setBounds(new Rectangle(182, 212, 85, 27));
jButton4.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(ActionEvent e) {
jButton4_actionPerformed(e);
jButton5.setText("Cancel");
jButton5.setBounds(new Rectangle(275, 212, 83, 27));
jMenu4.setText("Help");
jMenu5.setText("Help");
jMenuBar1.add(jMenu2);
jMenuBar1.add(jMenu1);
jMenuBar1.add(jMenu3);
jMenuBar1.add(jMenu5);
this.getContentPane().add(jButton1, null);
this.getContentPane().add(jButton2, null);
this.getContentPane().add(jButton3, null);
this.getContentPane().add(jLabel1, null);
this.getContentPane().add(jTextField1, null);
this.getContentPane().add(jButton4, null);
this.getContentPane().add(jButton5, null);
jMenuBar1.add(jMenu4);
jButton1.addActionListener(new ActionListener(){
void jButton4_actionPerformed(ActionEvent e) {
jButton4_actionPerformed(e);
void jButton2_actionPerformed(ActionEvent e) {
Container c=jButton4.getParent();
int i = JOptionPane.showConfirmDialog(c,"Do you really want to quit?",
"Quit?",JOptionPane.YES_NO_OPTION);
if(i == JOptionPane.YES_OPTION){
System.exit(0);
void jButton1_actionPerformed(ActionEvent e) {
Frame1 obj = new Frame1();
obj.setSize(600,600);
obj.show(true);
void jTextField1_actionPerformed(ActionEvent e) {
jTextField1_actionPerformed(e);
public void jButton4_actionPerformed(ActionEvent e) {
Database db = new Database();
String memId=jTextField1.getText();
if(memId.equals(""))
JOptionPane.showMessageDialog(null, "Enter Member ID!", "Hybrid Theory Mobile Computing System", JOptionPane.ERROR_MESSAGE);
else
try
Statement stmt = db.con.createStatement();
String delMem = "DELETE from member where id ='"+memId+"';";
stmt.executeUpdate(delMem);
db.con.close();
JOptionPane.showMessageDialog(null, "Member Successfully Deleted!", "Hybrid Theory Mobile Computing System", JOptionPane.INFORMATION_MESSAGE);
catch(SQLException f)
System.out.println("Error in Retriving record");
}

I noticed something:
jButton1.addActionListener(new ActionListener(){
void jButton4_actionPerformed(ActionEvent e) {
jButton4_actionPerformed(e);
}If you plan to use AWT's ActionListner, change that to:jButton1.addActionListener(new java.awt.event.ActionListener(){
void actionPerformed(ActionEvent e) {
jButton4_actionPerformed(e);
}Unless of course you have written your own ActionListener by the same name?

Similar Messages

  • Please help me debug this program unit!!!!!

    dear sir,
    i tried diligently to find and to debug this tiny program unit,although my observation to the coding rules of the packages ,compilation error still occur.
    therefore,kindly i'm asking you sir to learn me how to correct it.
    thank you.
    create or replace package test_pack is
    type emp_table_type is table of emp.sal%type
    index by binary_integer;
    emp_list emp_table_type;
    function test_sal
    (v_sal in emp.sal%type)
    return emp_table_type;
    end test_pack;
    create or replace package body test_pack is
    temp emp.sal%type;
    cursor emp_cursor is
    select sal from emp;
    i number :=1;
    j number :=1;
    function test_sal
    (v_sal in emp.sal%type)
    return emp_table_type
    is
    open emp_cursor;
    loop
    fetch emp_cursor into temp;
    if temp < v_sal then
    emp_list(i):=temp;
    bms_output.put_line('rowcount i='||emp_cursor%rowcount);
    dbms_output.put_line('iterator i='||i);
    i:=i+1;
    else
    dbms_output.put_line('rowcount j='||emp_cursor%rowcount);
    dbms_output.put_line('iterator j='||j);
    j:=j+1;
    end if;
    if emp_cursor%notfound then
    dbms_output.put_line('cursor closed...');
    close emp_cursor;
    return emp_list;
    exit;
    end if;
    end loop;
    end test_pack;

    You can use "show err" to show the errors after compilation errors occur:
    SQL> create or replace package test_pack is
      2    type emp_table_type is table of emp.sal%type index by binary_integer;
      3    emp_list emp_table_type;
      4    function test_sal(v_sal in emp.sal%type) return emp_table_type;
      5  end test_pack;
      6  /
    Package is aangemaakt.
    SQL> create or replace package body test_pack is
      2    temp emp.sal%type;
      3    cursor emp_cursor is
      4    select sal from emp;
      5    i number :=1;
      6    j number :=1;
      7
      8    function test_sal
      9    (v_sal in emp.sal%type)
    10    return emp_table_type
    11    is
    12      open emp_cursor;
    13      loop
    14        fetch emp_cursor into temp;
    15        if temp < v_sal then
    16          emp_list(i):=temp;
    17          bms_output.put_line('rowcount i='||emp_cursor%rowcount);
    18          dbms_output.put_line('iterator i='||i);
    19          i:=i+1;
    20        else
    21          dbms_output.put_line('rowcount j='||emp_cursor%rowcount);
    22          dbms_output.put_line('iterator j='||j);
    23          j:=j+1;
    24        end if;
    25        if emp_cursor%notfound then
    26          dbms_output.put_line('cursor closed...');
    27          close emp_cursor;
    28          return emp_list;
    29          exit;
    30        end if;
    31      end loop;
    32  end test_pack;
    33  /
    Waarschuwing: package-body is aangemaakt met compilatiefouten.
    SQL> show err
    Fouten voor PACKAGE BODY TEST_PACK:
    LINE/COL ERROR
    14/7     PLS-00103: Symbool "FETCH" aangetroffen terwijl een van de
             volgende werd verwacht:
             constant exception <een ID>
             <een scheidingsteken-ID tussen dubbele aanhalingstekens>
             table LONG_ double ref char time timestamp interval date
             binary national character nchar
    32/5     PLS-00103: Symbool "TEST_PACK" aangetroffen terwijl een van de
             volgende werd verwacht:
             ;To make your program compile, add a begin and end and fix the typo (in bold):
    SQL> create or replace package body test_pack is
      2    temp emp.sal%type;
      3    cursor emp_cursor is
      4    select sal from emp;
      5    i number :=1;
      6    j number :=1;
      7
      8    function test_sal
      9    (v_sal in emp.sal%type)
    10    return emp_table_type
    11    is
    12    begin
    13      open emp_cursor;
    14      loop
    15        fetch emp_cursor into temp;
    16        if temp < v_sal then
    17          emp_list(i):=temp;
    18          dbms_output.put_line('rowcount i='||emp_cursor%rowcount);
    19          dbms_output.put_line('iterator i='||i);
    20          i:=i+1;
    21        else
    22          dbms_output.put_line('rowcount j='||emp_cursor%rowcount);
    23          dbms_output.put_line('iterator j='||j);
    24          j:=j+1;
    25        end if;
    26        if emp_cursor%notfound then
    27          dbms_output.put_line('cursor closed...');
    28          close emp_cursor;
    29          return emp_list;
    30          exit;
    31        end if;
    32      end loop;
    33    end;
    34  end test_pack;
    35  /
    Package-body is aangemaakt.
    SQL> declare
      2    t test_pack.emp_table_type;
      3  begin
      4    t := test_pack.test_sal(2000);
      5    for i in 1..t.count
      6    loop
      7      dbms_output.put_line(t(i));
      8    end loop;
      9  end;
    10  /
    rowcount i=1
    iterator i=1
    rowcount i=2
    iterator i=2
    rowcount i=3
    iterator i=3
    rowcount j=4
    iterator j=1
    rowcount i=5
    iterator i=4
    rowcount j=6
    iterator j=2
    rowcount j=7
    iterator j=3
    rowcount j=8
    iterator j=4
    rowcount j=9
    iterator j=5
    rowcount i=10
    iterator i=5
    rowcount i=11
    iterator i=6
    rowcount i=12
    iterator i=7
    rowcount j=13
    iterator j=6
    rowcount i=14
    iterator i=8
    rowcount i=14
    iterator i=9
    cursor closed...
    800
    1600
    1250
    1250
    1500
    1100
    950
    1300
    1300
    PL/SQL-procedure is geslaagd.To fix the bug of the last iteration and put the variables in the sections they belong:
    SQL> create or replace package test_pack is
      2    type emp_table_type is table of emp.sal%type index by binary_integer;
      3    function test_sal(v_sal in emp.sal%type) return emp_table_type;
      4  end test_pack;
      5  /
    Package is aangemaakt.
    SQL> create or replace package body test_pack
      2  is
      3    function test_sal(v_sal in emp.sal%type) return emp_table_type
      4    is
      5      emp_list emp_table_type;
      6      temp emp.sal%type;
      7      cursor emp_cursor is select sal from emp;
      8      i number :=1;
      9      j number :=1;
    10    begin
    11      open emp_cursor;
    12      loop
    13        fetch emp_cursor into temp;
    14        if emp_cursor%notfound then
    15          dbms_output.put_line('cursor closed...');
    16          exit;
    17        end if;
    18        if temp < v_sal then
    19          emp_list(i):=temp;
    20          dbms_output.put_line('rowcount i='||emp_cursor%rowcount);
    21          dbms_output.put_line('iterator i='||i);
    22          i:=i+1;
    23        else
    24          dbms_output.put_line('rowcount j='||emp_cursor%rowcount);
    25          dbms_output.put_line('iterator j='||j);
    26          j:=j+1;
    27        end if;
    28      end loop;
    29      close emp_cursor;
    30      return emp_list;
    31    end;
    32  end test_pack;
    33  /
    Package-body is aangemaakt.
    SQL> declare
      2    t test_pack.emp_table_type;
      3  begin
      4    t := test_pack.test_sal(2000);
      5    for i in 1..t.count
      6    loop
      7      dbms_output.put_line(t(i));
      8    end loop;
      9  end;
    10  /
    rowcount i=1
    iterator i=1
    rowcount i=2
    iterator i=2
    rowcount i=3
    iterator i=3
    rowcount j=4
    iterator j=1
    rowcount i=5
    iterator i=4
    rowcount j=6
    iterator j=2
    rowcount j=7
    iterator j=3
    rowcount j=8
    iterator j=4
    rowcount j=9
    iterator j=5
    rowcount i=10
    iterator i=5
    rowcount i=11
    iterator i=6
    rowcount i=12
    iterator i=7
    rowcount j=13
    iterator j=6
    rowcount i=14
    iterator i=8
    cursor closed...
    800
    1600
    1250
    1250
    1500
    1100
    950
    1300
    PL/SQL-procedure is geslaagd.To be really efficient and not care about looping, using counters and dbms_output, and assuming the emp table won't ever be a big table (else use the LIMIT clause):
    SQL> create or replace package body test_pack
      2  is
      3    function test_sal(v_sal in emp.sal%type) return emp_table_type
      4    is
      5      emp_list emp_table_type;
      6    begin
      7      select sal bulk collect into emp_list
      8        from emp
      9       where sal < v_sal
    10      ;
    11      return emp_list;
    12    end;
    13  end;
    14  /
    Package-body is aangemaakt.
    SQL> declare
      2    t test_pack.emp_table_type;
      3  begin
      4    t := test_pack.test_sal(2000);
      5    for i in 1..t.count
      6    loop
      7      dbms_output.put_line(t(i));
      8    end loop;
      9  end;
    10  /
    800
    1600
    1250
    1250
    1500
    1100
    950
    1300
    PL/SQL-procedure is geslaagd.Hope it helps.
    Regards,
    Rob.

  • HELP TO DEBUG THE PROGRAM OF AGILENT6600X

    Hello,
              First let me simply introduce this program.
              The horizental toggle switch is used to set the default value to the power supply.
              The vertical slide switch is used to read the value from the power supply(after board boot up).
              The phenomenon is when i run the vi, always pop up the indicate message"the 9v PS ID can not be recognized". The problem is why always the problem happens on the 9v PS.
              I have to say this program is not so good, if anyone can give me some guidence, I'll be very appreciate. Thanks.
    Attachments:
    PS.vi ‏44 KB

    Good morning,
    Without the Agilent drivers (vi's), I could not see much about the code.   Do you only get this message with the 9V PS?
    Have you tried communicating with the instrument using MAX (Measurement & Automation Explorer)?  That should be the first step to make sure that communication can be achieved.  You could try a basic query like " *IDN? " and see what it returns.  It's under "Communicate With Instrument", when you look at the "Devices" list.
    Also try opening the actual Agilent VI's and monitor what is being sent over the GPIB. Compare it with the others that work.  You can copy the faulty command to MAX and communicate with the instrument using the command. 
    Hope this helps,
    RayR

  • Hi, I just installed my Creative Suite 6 and the programs close right after launching (for about 5 seconds) with no dialog box about an error. I have tried uninstalling and re-installing but still the same thing. Help pls!

    Hi, I just installed my Creative Suite 6 and the programs close right after launching (for about 5 seconds) with no dialog box about an error. I have tried uninstalling and re-installing but still the same thing. Help pls!

    Sign in, activation, or connection errors | CS5.5 and later
    Mylenium

  • I want parameter for program name entering with f4 help pls send  code

    I want parameter for program name entering with f4 help pls send code
    Points if helpful

    Hi,
    PROG is a string which indicates the type of the object --- program
    u can call the FM as follows
    CALL FUNCTION 'REPOSITORY_INFO_SYSTEM_F4'
      EXPORTING
    <b>    object_type                     =  'PROG'
       OBJECT_NAME               =  p_report</b>
      ENCLOSING_OBJECT                =
      SUPPRESS_SELECTION              = 'X'
      VARIANT                         = ' '
      LIST_VARIANT                    = ' '
      DISPLAY_FIELD                   =
      MULTIPLE_SELECTION              =
      SELECT_ALL_FIELDS               = ' '
      WITHOUT_PERSONAL_LIST           = ' '
    IMPORTING
      OBJECT_NAME_SELECTED            =
      ENCLOSING_OBJECT_SELECTED       =
      STRUCINF                        =
    TABLES
      OBJECTS_SELECTED                =
      RECORD_TAB                      =
    EXCEPTIONS
      CANCEL                          = 1
      WRONG_TYPE                      = 2
      OTHERS                          = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Patil

  • What transactions are helpful in debugging performance of a program

    What transactions help in debugging performance related issues of a custom program?

    Hi.... Gopal...,
         First rectify the errors and warning in ur program with...
    > SLIN -> Extended program Check
    > SCID -> Code Inspecter
        Then Analyze the performance level of ur program with...
    > SE30 -> Runtime analysis
        There you can study the actions of ur statements with Tracing the statements with...
    > ST05 -> SQL Trace
        Then do the modifications according to the issues...,
    Thank you,
    Naveen.I

  • Relating debugging of program.

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

    HI
        Debugger
    The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.
    Two types of debugging are currently possible: Debugging with the classic Debugger for release levels up to and including 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:
    ·         The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.
    The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means.
    The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.
    As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities  ® Settings. It is also possible to switch the Debugger at any time during a session under the menu option Debugging.
    As of Release 7.00, the new ABAP Debugger is the default.
    Breakpoints
    Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
    There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
    Breakpoint Variants
    The Debugger contains different breakpoint variants:
    Static
    A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
    Directly set
    dynamic breakpoints
    Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
    Breakpoints
    at statements
    The Debugger stops the program immediately before the specified statement is executed.
    Breakpoints
    at subroutines
    The Debugger stops the program immediately before the specified subroutine is called.
    Breakpoints at function modules
    The Debugger stops the program immediately before the specified function module is called.
    Breakpoints at methods
    The Debugger stops the program immediately before the specified method is called.
    Breakpoints at exceptions and system exceptions
    The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
    Static Breakpoints
    Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
    In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
    Dynamic Breakpoints
    Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
    Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
    ·        You do not have to change the program code.
    ·        You can set them even when the program is locked by another programmer.
    ·        You can define a counter that only activates the breakpoint after it has been reached.
    Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
    In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
    Lifetime and Transfer of Breakpoints
    A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
    If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
    If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging  under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
    For further information on special breakpoints, refer to:
    Breakpoints at Statements
    Breakpoints at Subroutines
    Breakpoints at Function Module Calls
    Breakpoints at Methods
    Breakpoints at System Exceptions
        Watchpoints
    Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
    Use
    You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
    Features
    ·        You can set up to five watchpoints in a program.
    See also Setting Watchpoints.
    ·        You can also specify the conditions under which a watchpoint is to become active.
    ·        You can specify a logical link for up to five (conditional) watchpoints.
    See also Specifying Logical Links.
    ·        You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
    ·        You can change and delete watchpoints.
    See Changing Watchpoints
    ·        You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
    See Memory Monitoring with Watchpoints
    REWARD IF HELPFUL
    vivekanand

  • Dbx to debug JNI programs stops on SIGUSR2

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

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

  • Send me with screenshots how to debug ABAP PROGRAMS !

    i NEED HELP IN aBAP DEBUDGGING AS I AM NEW TO THIS.
    pLEASE HELP ME

    Hi,
    Debuging means checking the functionality (line by line of your code) of your program at runtime.
    you can do it in below possible ways.
    1) Putting break-point in your program.
    select the line from where you want to debug in your program, put the cursor on that line and the choose 'stop' button in your application tool bar which will set's break point on that line, then execute that program it will take you to debug mode, in debug mode you can see the values in variables using 'fields' tab, and you can see the internal table records by choosing 'tables' tab, and you can put 'watch points'....etc.
    2) Putting '/H' command in your command box.
    which will take you to debug mode right from the first line of your code.
    put '/h' and press enter in your command box, and then execute your program it will goes to debug mode.
    3) write 'BREAK-POINT' code in your coding part.
    write the 'BREAK-POINT' code before your debug line, and then execute the code it will stops the execution of your program and it will take you to debug mode.
    Note:- don't use this option, if you forgot to remove this code, it will create some problems, it's better to avoid this option.
    4) Debugging SAP-Scripts.
    go to SE71 tcode, in the 'UTILITIES' option of your menu-bar options you  can find 'activate debugger' option select that option, while running that script it will take you to debug mode.
    once if your entered to debug mode, by doing some R&D you can easily find the available options.
    Reward if useful.
    Thanks,
    Sreeram.

  • Debugging driver program for SAP SCrIPT

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

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

  • HELP PLS! reprogram voicemail key (1) in nokia 880...

    HELP PLS!
    I need to reprogram the voicemail key (=1) in a nokia arte 8800 and dont know how!
    In the user manual it tells you to go to messaging... and there to voice messages... it looks easy and simple BUT this phone doesnt have that option in messaging... no "voice messages" in sight at all..!
    So I'm getting nuts and odnt know what else to do.
    Any ideas pls?!
    thanks

    Hmmm...on mine it does have the option, once in messages, then voicemail, under this option, there are only two, one of which is the voice mailbox number, this should be set to the number of your voicemail service (for Vodafone, it's 121).
    Do you not have this option? If not you could program the number as a speed dial which should then do the same.

  • Need help in debugging vf03

    Hi,
    i need your help in debugging the vf03 tcode. the senariou is as follows.
    in vf03 when i enter the billing document no. and press enter and then when i click on parter push button on the application toolbar and then click on ship-to-party item then under the field tax juridiction cde which is refering to txjcd field of vbadr table im getting the value as TAXUSX instead of a 10 digit value which is present in txjcd field of kna1 table for that particular customer.
    and this is happening only for few invoice no's not for all.
    i think that some where the data is getting changed or not properly communicated for some invoice numbers.
    i need help for where to start tracing and how to debug this error out and the flow logic of debugging.
    waiting for ur reply
    regards,
    maqsood

    Hi kahan,
    frist you have check with your function consultant is there are mataing the TAX for that countary .
    and come to debug.
    easyt way is take that screen field name(patha pres F1 and technical attributes ) and program name screen name .
    then seach that field in that program screen put break-point at that level and run tranction.
    stil you facing any problem send more details i will try to help you.
    Do Reward points..if found helpful
    thaks,
    saleem

  • Need help with debugging PLEASE

    Hi,
    I'm new to Java and was given an assignment to debug a program. I am completely lost and really havent gone over most of the stuff that is in this program. I would greatly appreciate any help with this that I can get.
    Here is my code:
    import java.util.*;
    import javax.swing.*;
    public class IndexHitFrequency
    private final int NUMBER_OF_SIMULATIONS = 1000;
    private int indexHit[] = new int [10];
    public IndexHitFrequency()
    Random generator = new Random(); // for generating random number
    int array[] = {6, 2, 4, 8, 5, 0, 1, 7, 3, 9 };
    //convert to ArrayList and sort it
    List list = new ArrayList(Arrays.asList(array));
    for (int i = 0; i < NUMBER_OF_SIMULATIONS; i++)
    //generate random number
    int randomNumber = generator.nextInt(array.length);
    // get index hit
    int index = Collections.binarySearch(list, randomNumber) ;
    // save index hit to array
    if(index > -1)
    indexHit[index]++;
    }//end for
    String output = "Index\tFrequency\t\n";
    //append the frequency of index hit to output
    for (int i = 0; i < indexHit.length; i++)
    output += i + "\t" + indexHit[i] + "\t\n";
    //display result
    JTextArea outputArea = new JTextArea();
    outputArea.setText(output);
    JOptionPane.showMessageDialog(null, outputArea, "Search random number 1000 times" ,
    JOptionPane.INFORMATION_MESSAGE);
    System.exit(0);
    }// end constructor
    public static void main (String [] args)
    new IndexHitFrequency();
    } // end class IndexHitFrequency
    I get these errors after trying to compile:
    "IndexHitFrequency.java": Error #: 300 : method asList(int[]) not found in class java.util.Arrays at line 17, column 40
    "IndexHitFrequency.java": Error #: 300 : method binarySearch(java.util.List, int) not found in class java.util.Collections at line 24, column 34

    C:\Java\Tutorial\rem>javac IndexHitFrequency.java
    IndexHitFrequency.java:15: asList(java.lang.Object[]) in java.util.Arrays cannot
    be applied to (int[])
    List list = new ArrayList(Arrays.asList(array));
                                    ^
    IndexHitFrequency.java:22: cannot find symbol
    symbol  : method binarySearch(java.util.List,int)
    location: class java.util.Collections
    int index = Collections.binarySearch(list, randomNumber) ;
                           ^
    2 errors
    C:\Java\Tutorial\rem>Copied source and compiled in DOS window ( XP's cmd.exe) and got these error messages...
    I think these error are more clear than the ones you posted, so this should help you resolve the problem...
    - MaxxDmg...
    - ' He who never sleeps... '

  • Need tips on debugging standard programs

    I am a beginner and my first project is a maintainence project. Debugging standard programs is getting too tough for me. Is it with everybody? Can you please suggest me some ways to make my task easier.
    The comments are in german and there are no explanation of ne step newhere. I cant even remember which program or include file i'm in.

    Hi,
    You can refer the below links to develop the debugging skills.
    debugging in standard progrms
    debugging
    http://help.sap.com/saphelp_nw04/helpdata/en/b3/d322540c3beb4ba53795784eebb680/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0
    http://www.sappro.com/downloads/Settings&SystemAreas.pdf
    Hope this will help to start with.
    Regards,
    Ferry Lianto

  • How to debug the program in background

    hi
    how to debug the program in background

    Hello everyone,
    I often debug my programs via the sm50 transaction and it works very well (especially when you put the dummy loop ^ - ^ ). However we are confronted to a major problem when more than one user tries to debug. We get a message saying that the maximum number of users in the debugging mode has been reached!! Thus we each have to wait for our turn to debug our program. It's a real pain.
    We've searched for a parameter to configure the number of users for the debugging mode but in vain
    Has anyone else had this kind of problem? If yes, what do I need to do to correct it?
    Any suggestion would be helpful as I am new to BW.
    Thank you beforehand.
    Regards,
    Dimple

Maybe you are looking for

  • My account was hacked in September -- Still no action from Verizon. Please help!

    My account was hacked in September, someone added an additional line and ordered an iPhone, adding more than $600 to my account. Verizon quickly identified this as fraud and assured me that my account would be cleaned up. Almost three months later, I

  • Setting up a small business network using mac and windows pcs

    Setting up a small business network using mac and windows??

  • Video Camera not detected through Firewire

    I've been having trouble connecting my video camera to my computer for importing video into Final Cut. After some deduction, my main conclusion/concern is that when I hook up my Canon minidv camera to the computer via firewire 400, it fails to show u

  • Outputting DVD Player to Television

    My home DVD player is dying slowly-about half of my collection no longer plays on it, but everything plays fine on my PowerBook. I was wondering if it's possible to plug my PB into my TV, and then output whatever is showing in DVD Player.app to the t

  • Advice on printing large photos?

    I have a Canon PowerShot SD400 Digital Elph camera. As far as I can tell, the largest it can take is 2592 x 1944, which shows up as 180 dpi when I open it in Photoshop. Based on this, I think that the largest standard size I can order is 10" x 8" thr