Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7913699
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T13:54:21+00:00 2026-06-03T13:54:21+00:00

I am a little new to the format of Dalvik bytecode, I am wonering

  • 0

I am a little new to the format of Dalvik bytecode, I am wonering what do these *-bearing register mean, e.g. object-bearing, exception-bearing, etc.

At the same time, the generated bytecode is using type, not registers? For example,

throws Landroid/database/SQLException is generated, but the Landroid/database/SQLException is a type, then why instruction summary says throw vAA where vAA is exception-bearing register?
Am I missing something?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T13:54:22+00:00Added an answer on June 3, 2026 at 1:54 pm

    This simply refers to the type of data that the instruction holds. The vm must be able to determine statically that the register contains that type of data at that point. In other words, that for all incoming code paths, that register has been set to that type of data.

    If you want to investigate how register type information is propagated in more detail, you can decompile your application with baksmali using the -r option, which will output comments before/after each instruction with information on the register types for the registers that are relevant for that instruction. This information should match the register type information that the vm builds internally, in the bytecode verifier.

    For example, say you have a method that simply contains:

    const-string v0, "Hello World!"
    throw v0
    

    This would not be allowed, because at the point of the throw instruction, the p0 register does not contain a reference to an object that extends from Throwable (i.e. it is not “an exception-bearing register”).

    If you use -r in baksmali, you will see:

    #v0=(Uninit);
    const-string v0, "Hello World!"
    #v0=(Reference,Ljava/lang/String;);
    
    #v0=(Reference,Ljava/lang/String;);
    throw v0
    

    Which clearly shows that v0 does not contain an exception at the point of the throw instruction.

    Additionally, something like this would not be allowed:

    #v0=(Uninit);
    new-instance v0, Ljava/lang/Exception;
    #v0=(UninitRef,Ljava/lang/Exception;);
    
    #v0=(UninitRef,Ljava/lang/Exception;);
    invoke-direct {v0}, Ljava/lang/Exception;-><init>()V
    #v0=(Reference,Ljava/lang/Exception;);
    
    #p0=(Integer);
    if-eqz p0, :cond_9
    
    #v0=(Reference,Ljava/lang/Exception;);
    const-string v0, "Hello World!"
    #v0=(Reference,Ljava/lang/String;);
    
    :cond_9
    #v0=(Reference,Ljava/lang/Object;);
    throw v0
    

    Because at the point of the throw, v0 might contain either an exception, or a string. In this case, it reports the “type” of v0 as Ljava/lang/Object;, because that is the common parent class of both types.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I made this little function: public String getDay() { String day = (String)android.text.format.DateFormat.format(E, new
Ok, a little new to JSON format.. I have the following JSON string returned
A little new to EF, so please bear with me if the answer to
hello i am little new to all this but i want to know that:
I am a little new to android/java. I am trying to pass JSON values
I'm a little new to Wordpress, and I'm using one of the default theme.
I am having a new little problem; I have a little pointer called: int
I am still a little bit new to C# and I was wondering how
am new to Json so a little green. I have a Rest Based Service
I'm new around here and i have a little problems with a C# application.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.