Databases
StackOverflow2013
Postsdbo
POWhen does the JVM omit line info in a stack trace and how can I prevent it?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
    primarykey
    data
    text
    <p>I have a very confusing situation:</p> <p>I have a class that is compiled with line info on (verified using <code>javap -l</code>). This class gets loaded and instrumented with ASM. I verified that the correct class is loaded (i.e. not a stale class file from somewhere else). And I also made sure that the ASM flag <code>ClassReader.SKIP_DEBUG</code> is not set. Now if I call <code>Thread.currentThread().getStackTrace()</code>, I get <code>StackTraceElement</code>s concerning this class that miss the line info. When debugging in Eclipse, the line info shows in the stack trace. I also made sure that the JVM is started with <code>-Xint</code> just to make sure the info is not erased as a optimization when the code is JIT compiled.</p> <p>And most confusing: although all classes are loaded and instrumented the same, this is only true for some classes, not for all. This is the main reason, why I think this has got something to do with the JVM.</p> <p>So my question is: does the JVM omit line info in the stack trace, if so when and how can I prevent this?</p> <p><strong>Edit:</strong> Just to make things clear: This is the class file of the source file I have in front of me, not of a 3rd party library. And as should be clear from above I tried hard to make sure the info is in the bytecode.</p> <p><strong>Edit:</strong> Now I even found an example where one <code>StackTraceElement</code> has line number info and another one hasn't and they are concerned with different methods <strong><em>from the same class</em></strong>!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USroesslerj
    1. USroesslerj
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo the classes with omitted line numbers have anything in common (same package/jar)?
      singulars
      1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
      1. USTMN
    2. COAre you doing the instrumenting? And if yes, are you updating the `LineNumberTable` to compensate for any bytecodes that you're adding?
      singulars
      1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
      1. USparsifal
    3. COIn theory you could have the whole HelloWorld example in one line, Java is not enforcing line breaks. Thus I don't see how adding bytecode should interfere with the line number info... or am I missing something here?
      singulars
      1. POWhen does the JVM omit line info in a stack trace and how can I prevent it?
      1. USroesslerj
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload