pdk/docs/source/report-bugs.jd

page.title=Report Bugs
doc.type=source
@jd:body
<div>
<p>Thanks for your interest in Android! One of the best ways you can help us
improve Android is to let us know about any problems you find with it.</p>
<p>First, though: if you think you've found a security vulnerability,
<b>please don't use the forms below</b>. (Using the public forms below may
allow anyone to see your report, which may put users at risk until the bug is
fixed.) Instead, please report security bugs to our security team by emailing
<a href="mailto:security@android.com">security@android.com</a>.  We believe in
responsible disclosure of security vulnerabilities, and will give you proper
attribution for any issues you report.</p>
<p>Here's how to report non-security bugs:</p>
<ol>
  <li><a href="http://code.google.com/p/android/issues/advsearch">Search for
  your bug</a> to see if anyone has already reported it.</li>
  <li>If you find your issue and it's important to you, star it! That's how we
  know which bugs are most important to fix.</li>
  <li>If no one's reported your bug, file the bug. You can use one of these
  templates:<ul>
    <li><a
    href="http://code.google.com/p/android/issues/entry?template=User%20bug%20report">Bugs
    in your Device (for users)</a> - use this if you want to report a bug in a
    device you own</li>
    <li><a
    href="http://code.google.com/p/android/issues/entry?template=Developer%20bug%20report">Bugs
    in the Software (for developers)</a> - use this if you found a bug in the
    course of developing an app</li>
    <li><a
    href="http://code.google.com/p/android/issues/entry?template=Feature%20request">Request
    a New Feature</a> - use this for a feature you'd like to see in a future
    verison</li>
  </ul></li>
</ol>
<p>Please note that we can't guarantee that any particular bug can be fixed in
any particular release. To see what happens to your bug once you report it,
read <a href="{@docRoot}source/life-of-a-bug.html">Life of a Bug</a>.</p>
<p>In general, please put as much info in bugs as you can. Just a one liner
telling us something isn't working is usually useless, and will probably be
closed without any action. The more detail you provide, the more likely your
issue is to be resolved. Below, there are some examples of a good bug report
and a poor bug report.</p>
<h3>A Poor Bug Report</h3>
<pre>
Title: Error message

When running Eclipse I get an "Internal Error" that says "See the .log file
for more details".

Steps to reproduce:
Happens when "Object o = null". Doesn't happen when changed to "Object o".

Expected results:
I wouldn't get the error message--would work with Object o = null.

Observed results:
See above.
</pre>
<p>This is a poor bug report because it doesn't provide any context for the
issue; is it a problem in the Dalvik virtual machine, the core framework, or
something else? It also doesn't provide any code or hint on how to reproduce
it. In other words, this bug report doesn't provide enough information for
anyone to take action on, so it would be ignored.</p>
<h3>A Good Bug Report</h3>
<pre>
Title: Stepping over "Object o = null" causes Eclipse "Internal Error"

Interesting bug, while using Eclipse 3.3.1.1 with m37a of android and
the following code:

package com.saville.android;

import android.app.Activity;
import android.os.Bundle;
import android.util.Log;

public class TestObjectNull extends Activity {
    /** Called when the activity is first created. */
    &#64;Override
    public void onCreate(Bundle icicle) {
        super.onCreate(icicle);
        setContentView(R.layout.main);

        Object o = null;

        o = "hi";

        Log.v(TAG, "o=" + o);
    }

    static final String TAG = "TestObjectNull";

}

Eclipse indicates an "Internal Error" with "See the .log file for more
details" and then asks if I want to exit the workbench. This occurs when I
place a break point on "setContentView(R.layout.main);" and then single
step over "Object o = null;"

If I change "Object o = null;" to "Object o" all is well.

The last lines of the .log file are:

!ENTRY org.eclipse.core.jobs 4 2 2008-01-01 13:04:15.825
!MESSAGE An internal error occurred during: "has children update".
!STACK 0
java.lang.InternalError: Invalid signature: "&lt;null&gt;"
        at
org.eclipse.jdi.internal.TypeImpl.signatureToTag(TypeImpl.java:307)
        at
org.eclipse.jdi.internal.LocalVariableImpl.tag(LocalVariableImpl.java:185)
        at
org.eclipse.jdi.internal.StackFrameImpl.getValues(StackFrameImpl.java:128)
        at
org.eclipse.jdi.internal.StackFrameImpl.getValue(StackFrameImpl.java:73)
        at
org.eclipse.jdt.internal.debug.core.model.JDILocalVariable.retrieveValue(JDILocalVariable.java:57)
        at
org.eclipse.jdt.internal.debug.core.model.JDIVariable.getCurrentValue(JDIVariable.java:66)
        at
org.eclipse.jdt.internal.debug.core.model.JDIVariable.getValue(JDIVariable.java:88)
        at
org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.hasChildren(VariableContentProvider.java:62)
        at
org.eclipse.jdt.internal.debug.ui.variables.JavaVariableContentProvider.hasChildren(JavaVariableContentProvider.java:73)
        at
org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.updateHasChildren(ElementContentProvider.java:223)
        at
org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$3.run(ElementContentProvider.java:200)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
</pre>
</div>