Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by guwirth
, 1 year ago
Unable to analyze file:
via GitHub by tomikais
, 1 year ago
Unable to analyze file:
via GitHub by Riruk
, 7 months ago
Unable to analyze file: PATH-TO-Mozilla_Source/obj-x86_64-pc-linux-gnu/dist/include/nsISupportsBase.h
via GitHub by robenj
, 1 year ago
Unable to analyze file: /var/projects/sonar/x/x/x/x/x.cxx
via GitHub by jmecosta
, 1 year ago
Unable to analyze file: E:\prod\structures\src\work\Core\Common\libfilesystem\tool_sys_io_util.cpp
via GitHub by robenj
, 1 year ago
Unable to analyze file: /home/webadm/sonar-cxx-refactor-highlighting/sonar-cxx-plugin/src/test/resources/org/sonar/plugins/cxx/highlighter.cc
java.lang.IllegalArgumentException: 104 is not a valid line offset for pointer. FileoduleKey=tekla.structures.core:Common, relative=libfilesystem/tool_sys_io_util.cpp, basedir=E:\prod\structures\src\work\Core\Common] has 60 character(s) at line 292	at org.sonar.api.internal.google.common.base.Preconditions.checkArgument(Preconditions.java:148)	at org.sonar.api.batch.fs.internal.DefaultInputFile.checkValid(DefaultInputFile.java:218)	at org.sonar.api.batch.fs.internal.DefaultInputFile.newPointer(DefaultInputFile.java:209)	at org.sonar.api.batch.fs.internal.DefaultInputFile.newRange(DefaultInputFile.java:240)	at org.sonar.api.batch.sensor.highlighting.internal.DefaultHighlighting.highlight(DefaultHighlighting.java:96)