decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Java bytecode contains symbolic references | 197 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Do we know that '104 came out of the java project?
Authored by: gdeinsta on Sunday, May 13 2012 @ 03:06 PM EDT

I don't recall.

[ Reply to This | Parent | # ]

  • for sure - Authored by: Anonymous on Sunday, May 13 2012 @ 03:10 PM EDT
    • for sure - Authored by: Anonymous on Sunday, May 13 2012 @ 03:14 PM EDT
    • for sure - Authored by: Anonymous on Sunday, May 13 2012 @ 03:17 PM EDT
Java bytecode contains symbolic references
Authored by: jbb on Sunday, May 13 2012 @ 04:06 PM EDT
Advanced obfuscation techniques for Java bytecode:
In order to achieve platform independence, instead of the traditional memory addresses, Java uses symbolic references to link entities from different libraries (including the standard and proprietary libraries). Therefore, the names of types, fields, and methods are stored in a constant pool within a bytecode file (Engel, 1999; Lindholm and Yellin, 1999; Meyer and Downing, 1997; Venners, 1998). These names and the simple stack-machine instructions facilitate the decompilation of the bytecode file.
Practical Java Game programming:
After a class has been loaded and verified, an implementation of a VM may choose to resolve its symbolic references.
I believe you are correct that the symbols are not stored in the instructions. Instead, they are stored in data space and the instructions only contain a fixed-length offset into that data space. The same is true for strings such as "Hello World". If you restrict the definition of "Java bytecode" to mean just the bytecode instructions themselves then, yes, there are no literal strings there, only indexes to strings. But if you use "Java bytecode" to mean the entire bytecode output of the Java compiler (.class files) then strings and symbols are included. The dx tool converts .class files to .dex files so the symbols do exist in the input to dx.

IIUC, the symbol strings are there in the .class files but in the optimization phase of the dx tool under discussion, Google does not actually make use of them.

---
Our job is to remind ourselves that there are more contexts
than the one we’re in now — the one that we think is reality.
-- Alan Kay

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )