[Bug java/16439] New: gcj doesn't generate proper debugging line number info

["jjohnstn at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>]

For the following test case in the gdb testsuite: jmain.java

public class jmain
{
  public static void main (String[] args)
    {
        return;
    }
}

The breakpoint for main ends up being line 4 (the open brace) instead of line 5.
 This does not match the C/C++ behavior which is to point to the first statement
of the member function.  Gdb gets the line number info from the compiler which
is the following tailed output from readelf -wl

 Line Number Statements:
  Extended opcode 2: set Address to 0x8048868
  Special opcode 8: advance Address by 0 to 0x8048868 and Line by 3 to 4
  Special opcode 89: advance Address by 6 to 0x804886e and Line by 0 to 4
  Special opcode 175: advance Address by 12 to 0x804887a and Line by 2 to 6
  Special opcode 28: advance Address by 2 to 0x804887c and Line by -5 to 1
  Special opcode 89: advance Address by 6 to 0x8048882 and Line by 0 to 1
  Advance PC by 14 to 8048890
  Extended opcode 1: End of Sequence

-- 
           Summary: gcj doesn't generate proper debugging line number info
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jjohnstn at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16439