[jira] Created: (RVM-847) Stack trace line numbers incorrect for inlined call sites

View: New views
2 Messages — Rating Filter:   Alert me  

[jira] Created: (RVM-847) Stack trace line numbers incorrect for inlined call sites

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Stack trace line numbers incorrect for inlined call sites
---------------------------------------------------------

                 Key: RVM-847
                 URL: http://jira.codehaus.org/browse/RVM-847
             Project: RVM
          Issue Type: Bug
          Components: Runtime
            Reporter: Michael Bond
            Assignee: Michael Bond


Stack traces in inlined methods don't have the correct line numbers in some cases.  For example, given this class

public class Blah {
  public static void main(String[] args) {
    method1();
  }
  static void method1() {
    method2();
    method3();
  }
  static void method2() { new Exception().printStackTrace();  }
  static void method3() { new Exception().printStackTrace();  }
}

and this command line:

dist/production_ia32-linux/rvm -X:aos:initial_compiler=opt -cp .. Blah

The resulting output shouldn't have the same line number (6) for the two call sites in method1:

java.lang.Exception
   at java.lang.Exception.<init>(Exception.java:66)
   at Blah.method2(Blah.java:9)
   at Blah.method1(Blah.java:6)
   at Blah.main(Blah.java:3)
java.lang.Exception
   at java.lang.Exception.<init>(Exception.java:66)
   at Blah.method3(Blah.java:10)
   at Blah.method1(Blah.java:6)
   at Blah.main(Blah.java:3)

Fix and explanation coming soon :)


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Jikesrvm-issues mailing list
Jikesrvm-issues@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-issues

[jira] Closed: (RVM-847) Stack trace line numbers incorrect for inlined call sites

by JIRA jira@codehaus.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ http://jira.codehaus.org/browse/RVM-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bond closed RVM-847.
----------------------------

    Resolution: Fixed

Fixed in r15762.  Stack-walking for inlined methods needs to compute bci for each call site.  Based on stack-walking code in
RVMThread.dumpStack().

> Stack trace line numbers incorrect for inlined call sites
> ---------------------------------------------------------
>
>                 Key: RVM-847
>                 URL: http://jira.codehaus.org/browse/RVM-847
>             Project: RVM
>          Issue Type: Bug
>          Components: Runtime
>            Reporter: Michael Bond
>            Assignee: Michael Bond
>
> Stack traces in inlined methods don't have the correct line numbers in some cases.  For example, given this class
> public class Blah {
>   public static void main(String[] args) {
>     method1();
>   }
>   static void method1() {
>     method2();
>     method3();
>   }
>   static void method2() { new Exception().printStackTrace();  }
>   static void method3() { new Exception().printStackTrace();  }
> }
> and this command line:
> dist/production_ia32-linux/rvm -X:aos:initial_compiler=opt -cp .. Blah
> The resulting output shouldn't have the same line number (6) for the two call sites in method1:
> java.lang.Exception
>    at java.lang.Exception.<init>(Exception.java:66)
>    at Blah.method2(Blah.java:9)
>    at Blah.method1(Blah.java:6)
>    at Blah.main(Blah.java:3)
> java.lang.Exception
>    at java.lang.Exception.<init>(Exception.java:66)
>    at Blah.method3(Blah.java:10)
>    at Blah.method1(Blah.java:6)
>    at Blah.main(Blah.java:3)
> Fix and explanation coming soon :)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Jikesrvm-issues mailing list
Jikesrvm-issues@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-issues