harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Frey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4514) [drlvm][jit][opt] Wrong line numbers in stack traces
Date Mon, 23 Jul 2007 21:35:31 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Frey updated HARMONY-4514:
------------------------------------

    Attachment: TraceTest.java

I noticed this issue while running the test attached to HARMONY-4513.

I tried throwing some exceptions but couldn't produce wrong line numbers that way.
So I've written another junit test (attached) and again the line numbers reported while running
with -Xem:opt didn't match with the line numbers of the assert* methods, while running with
-Xem:interpreter the line numbers are correct.
interpreter: 10; 19; 28; 37; 46
opt: 7; 19; 25; 34; 43
The interesting part is the second method in the test: interpreter and opt both report the
correct line number (the call of fail()).

> [drlvm][jit][opt] Wrong line numbers in stack traces
> ----------------------------------------------------
>
>                 Key: HARMONY-4514
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4514
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: WindowsXP, AthlonXP
>            Reporter: Alexander Frey
>            Assignee: Mikhail Fursov
>         Attachments: TraceTest.java
>
>
> While running some JUnit tests with the latest snapshot (r557495) and Eclipse 3.3 I noticed
wrong line numbers in the stack traces of the failed tests. It seems always the first line
of the test method is reported instead of the failing line.
> The issue occures w/o parameters and with -Xem:opt. I can't test it with -Xem:jet because
java returns immediately w/o running or reporting any error (issue with Harmony on WinXP+AthlonXP?).
> Running the same tests with -Xem:interpreter or with the M2 build the correct lines are
reported.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message