Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong line number in some cases. #2

Open
CoolTomatos opened this issue Dec 6, 2019 · 1 comment
Open

Wrong line number in some cases. #2

CoolTomatos opened this issue Dec 6, 2019 · 1 comment

Comments

@CoolTomatos
Copy link

CoolTomatos commented Dec 6, 2019

For example:

In MATH-101b:

377 | if (
378 |     source.substring(startIndex, endIndex).compareTo(
379 |     getImaginaryCharacter()) != 0) {
380 |     // set index back to initial, error index should be the start index
381 |     // character examined.
382 |     pos.setIndex(initialIndex);
383 |     pos.setErrorIndex(startIndex);
384 |     return null;
385 | }

The exception is thrown from substring(int, int) at line 378, but in JCrashPack it was logged as 377.

In LANG-44b:

193 | if (dec == null
194 |     && exp == null
195 |     && (numeric.charAt(0) == '-' && isDigits(numeric.substring(1)) || isDigits(numeric))) {
196 |     try {
197 |         return createLong(numeric);
198 |     } catch (NumberFormatException nfe) {
199 |         //Too big for a long
200 |     }
201 |     return createBigInteger(numeric);
202 |
203 | }

The exception is actually thrown from charAt(int) at line 195, but in JCrashPack it was logged as 193

@aryan7778
Copy link

aryan7778 commented Apr 23, 2020

@CoolTomatos It is showing that line no. which is the beginning of block of code that is throwing exception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants