Databases
StackOverflow2013
Usersdbo
USPeter
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USPeter
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. POInjecting code in an existing method using BCEL
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COThanks a lot @Holger! Removing the LocalVariableTypeTable fixed it! Simply calling the MethodGen's `removeLocalVariables()` at the end of the injecting made it work!
      singulars
      1. PO
      1. USPeter
    2. CO@Katona no i'm not building my own profiler. I'm using several existing profilers (xprof, hprof, yourkit, jprofiler and an experimental profiler) and compare their output to see if they recognize injected (and therefor slower) methods and how it impacts their results. I know JVMTI a little, if I remember correctly it provides a way to inject bytecode (for instance on class load) but the actual injecting part is not provided and has to happen by frameworks like BCEL (source: http://www.javalobby.org/java/forums/t19309.html).
      singulars
      1. POInjecting code in an existing method using BCEL
      1. USPeter
    3. CO@Antimony thats what I assume as well since an earlier bug with not counting parameters stack positions gave the same error. However what I don't know is where to look for. I was hoping for some tips. What can I have overlooked in the injecting bytecode in an existing method that causes some methods to be injected successfully while others cause the program to crash (like seen above) I've uploaded the class file ( original and injected broken one: http://we.tl/RydYOAgufK ). Be aware that you probably have to rename the injected one to the original name otherwise JD-GUI will show the old one..
      singulars
      1. POInjecting code in an existing method using BCEL
      1. USPeter
 

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