[android-developers] Re: Changing package names fubars the map overlays?
Dianne Hackborn wrote: This is the cause as shown in the stack crawl: E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException E/AndroidRuntime( 583): at org.apache.harmony.luni.util. FloatingPointParser.parseDouble(FloatingPointParser.java:254) E/AndroidRuntime( 583): at java.lang.Double.parseDouble(Double.java:332) E/AndroidRuntime( 583): at com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275) E/AndroidRuntime( 583): at com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141) E/AndroidRuntime( 583): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122) E/AndroidRuntime( 583): at android.app.ActivityThread.performLaunchActivity( What's the line at MainMap.java:275? -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
Faber Fedor wrote: Assume I'm a idio^H^H^H^Hn00b and explain it to me, please. I don't see what you do. Sorry, I forgot to elaborate this point in my earlier post. In Android, in effect, a stack trace contains two separate traces, and you want the second one. The second one is flagged as Caused by: and the exception: E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException followed by the stack trace corresponding to that exception: E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException E/AndroidRuntime( 583): at org.apache.harmony.luni.util. FloatingPointParser.parseDouble(FloatingPointParser.java:254) E/AndroidRuntime( 583): at java.lang.Double.parseDouble(Double.java:332) E/AndroidRuntime( 583): at com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275) E/AndroidRuntime( 583): at com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141) E/AndroidRuntime( 583): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122) E/AndroidRuntime( 583): at android.app.ActivityThread.performLaunchActivity( The upper stack trace is internal to Android itself and, at least for me, offers no meaningful information. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
On Wed, Jan 21, 2009 at 7:44 AM, Mark Murphy mmur...@commonsware.comwrote: In Android, in effect, a stack trace contains two separate traces, and you want the second one. The second one is flagged as Caused by: and the exception: I was seeing them as one stack and I thought the top of the stack had rolled off and was replaced by ...11 more. So the rule of thumb for the moment is to find the Caused by: and look for the line of my code closest to it. :-) Turns out the problem wasn't with changing the package name; I just happened to be working on that when the real problem of bad data appeared. It's interesting when your debug procedure requires you to leave the (desktop) computer! Thanks for all your help. -- Faber Fedor Cloud Computing New Jersey http://cloudcomputingnj.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
On Wed, Jan 21, 2009 at 4:44 AM, Mark Murphy mmur...@commonsware.comwrote: In Android, in effect, a stack trace contains two separate traces, and you want the second one. The second one is flagged as Caused by: and the exception: This is actually just standard Java behavior, printing the the various nested exceptions that way. You happen to see this form of the app stack crawl nested inside of the system a lot because the framework catches all exceptions coming out of the app when it calls into it, and creates a new exception tagging on additional information (the component that was being called when the exception happened). So always be sure to look down to the lowest-level caused by section for exactly where the error happened, and then you can work up from there if needed. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
Faber Fedor wrote: This is odd. I need to make my code pretty, so the first thing I want to do is to change the all the strings 'com.appspot.lbtdl' to 'com.faberfedor.tagyourworld'. I change every string in all the directories using the Perl 'pie' technique. Then I put the code into a new directory, create a new Eclipse project and run it. For some reason, my code now crashes with a NullPointerException in my MapView on the line map.getOverlays().add(new SitesOverlay(marker)); If I comment it out, the programs runs; wrongly, but it runs. Both map and marker have values/content/attributes/whatever you say a non-null object has. I've diffed every file in the project and the *only* thing different is the changing of my package name strings and the dir structure under src/. Any ideas? Various random ideas, and forgive me if you thought of these already: 1. Blow away R.java, assuming you copied it over with the rest of your code, and rebuild. 2. I assume your code is in a new directory tree (src/com/faberfedor/tagyourworld) that matches your namespace...right? 3. If you somehow copied over compiled classes when you set up your new Eclipse project, get rid of those too and make sure it rebuilds all from scratch. 4. Is the exception precisely on that line, or on a nested call? If it is precisely on that line, and if map and marker are confirmed to exist, then map.getOverlays() must be what's returning null. 5. Are you still inheriting from MapActivity? -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
On Tue, Jan 20, 2009 at 8:21 PM, Mark Murphy mmur...@commonsware.comwrote: Various random ideas, and forgive me if you thought of these already: 1. Blow away R.java, assuming you copied it over with the rest of your code, and rebuild. 2. I assume your code is in a new directory tree (src/com/faberfedor/tagyourworld) that matches your namespace...right? Did/verified both of those before writing to y'all... 3. If you somehow copied over compiled classes when you set up your new Eclipse project, get rid of those too and make sure it rebuilds all from scratch. I assume that was the stuff in the bin directory I blew away, right? 4. Is the exception precisely on that line, or on a nested call? How do I tell the difference? If it is precisely on that line, and if map and marker are confirmed to exist, then map.getOverlays() must be what's returning null. Now why would it do that? 5. Are you still inheriting from MapActivity? Yeah. As I said, the only thing(s) that changed are the package name strings. :-? -- Faber Fedor Cloud Computing New Jersey http://cloudcomputingnj.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
Faber Fedor wrote: 4. Is the exception precisely on that line, or on a nested call? How do I tell the difference? It'd be the top line in the stack trace, after the exception name/message. If, however, there are a few Android source lines, then yours, then your statement triggered the exception, but the exception itself happened somewhere in something you called. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
On Tue, Jan 20, 2009 at 8:41 PM, Mark Murphy mmur...@commonsware.comwrote: Faber Fedor wrote: 4. Is the exception precisely on that line, or on a nested call? How do I tell the difference? It'd be the top line in the stack trace, after the exception name/message. Are you talking in DDMS? I can't get threads or the heap working in there. Right before I execute the line, I see my MainMap.onCreate at the top of the stack with Instrumentation.callActivityOnCreate just below it. As soon as I step over it, it looks like my stack has been entirely replaced; at the top of the stack are several calls related to ActivityThread, looks like it's launching a new Activity. And while I am ActivityThread.performLaunchActivity, the exception gets thrown. -- Faber Fedor Cloud Computing New Jersey http://cloudcomputingnj.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
Forgive the lengthy response. You probably know all of this already and we're just getting hung up on nomenclature... Faber Fedor wrote: It'd be the top line in the stack trace, after the exception name/message. Are you talking in DDMS? I can't get threads or the heap working in there. I'm talking about the stack trace. The exception. Use adb logcat, DDMS, Eclipse, I don't care -- it's the place that tells you this thing went blooey and shows you all the methods, from the particular line that had the exception up the call stack, where you were at the time. And while I am ActivityThread.performLaunchActivity, the exception gets thrown. That is probably the bottom of the stack trace. I'm interested in the top. For example, from http://www.devdaily.com/java/edu/pj/pj010009/pj010009.shtml java.io.FileNotFoundException: fred.txt at java.io.FileInputStream.init(FileInputStream.java) at java.io.FileInputStream.init(FileInputStream.java) at ExTest.readMyFile(ExTest.java:19) at ExTest.main(ExTest.java:7) In this case, ExText.readMyFile is the line that triggered the exception. However, the exception itself occurred two calls deeper, in the bowels of java.io.FileInputStream's constructor. For many exceptions, this isn't that big of an issue -- you can think of ExText.readMyFile as being where the exception occurred. For NullPointerException, though, it really helps to know the the line in which the exception was raised -- the first line reported below the exception. Why? Because *that's* the line that attempted to access a null object. So, rolling all the way back to your code, if the first line in the stack trace below the exception is the line you cited (map.getOverlays().add(new SitesOverlay(marker));), then you know that *that line* attempted to use a null object, meaning that either map or map.getOverlays() returns a null. If, however, there are other lines between the exception and the above-quoted statement, that means your code may have *passed in* a null, and so either marker is null or somehow SitesOverlay is having problems and can't be instantiated. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training in Sweden -- http://www.sotrium.com/training.php --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
On Tue, Jan 20, 2009 at 9:11 PM, Mark Murphy mmur...@commonsware.comwrote:
That is probably the bottom of the stack trace. I'm interested in the top.
I've pasted the output of logcat, trimmed beneath my sig. Unfortunately,
the top of the stack trace reads:
E/AndroidRuntime( 583):at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.ja
va:1122)
E/AndroidRuntime( 583):at
android.app.ActivityThread.performLaunchActivity(ActivityThread.jav
a:2103)
E/AndroidRuntime( 583):... 11 more
which I take to mean we're not going to find out. :-)
So I'm going to try doing this all over again, more methodically, tomorrow
on my Linux box.
--
Faber Fedor
Cloud Computing New Jersey
http://cloudcomputingnj.com
--- BEGIN LOGCAT OUTPUT
D/AndroidRuntime( 583): Shutting down VM
W/dalvikvm( 583): threadid=3: thread exiting with uncaught exception
(group=0x40010e28)
E/AndroidRuntime( 583): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime( 583): java.lang.RuntimeException: Unable to start
activity
ComponentInfo{com.faberfedor.tagyourworld/com.faberfedor.tagyourworld.MainMap}:
java.lang.NullPointerException
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2140)
E/AndroidRuntime( 583): at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2156)
E/AndroidRuntime( 583): at
android.app.ActivityThread.access$1800(ActivityThread.java:112)
E/AndroidRuntime( 583): at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1580)
E/AndroidRuntime( 583): at
android.os.Handler.dispatchMessage(Handler.java:88)
E/AndroidRuntime( 583): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 583): at
android.app.ActivityThread.main(ActivityThread.java:3742)
E/AndroidRuntime( 583): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 583): at
java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497)
E/AndroidRuntime( 583): at dalvik.system.NativeStart.main(Native
Method)
E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 583): at
org.apache.harmony.luni.util.FloatingPointParser.parseDouble(FloatingPointParser.java:254)
E/AndroidRuntime( 583): at
java.lang.Double.parseDouble(Double.java:332)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141)
E/AndroidRuntime( 583): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122)
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2103)
E/AndroidRuntime( 583): ... 11 more
I/Process ( 54): Sending signal. PID: 583 SIG: 3
I/dalvikvm( 583): threadid=7: reacting to signal 3
I/dalvikvm( 583): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 583): Sending signal. PID: 583 SIG: 9
I/ActivityManager( 54): Process com.faberfedor.tagyourworld (pid 583) has
died.
--- END LOGCAT OUTPUT
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
This is the cause as shown in the stack crawl:
E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 583): at org.apache.harmony.luni.util.
FloatingPointParser.parseDouble(FloatingPointParser.java:254)
E/AndroidRuntime( 583): at
java.lang.Double.parseDouble(Double.java:332)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141)
E/AndroidRuntime( 583): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122)
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(
On Tue, Jan 20, 2009 at 6:51 PM, Faber Fedor faberfe...@gmail.com wrote:
On Tue, Jan 20, 2009 at 9:11 PM, Mark Murphy mmur...@commonsware.comwrote:
That is probably the bottom of the stack trace. I'm interested in the top.
I've pasted the output of logcat, trimmed beneath my sig. Unfortunately,
the top of the stack trace reads:
E/AndroidRuntime( 583):at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.ja
va:1122)
E/AndroidRuntime( 583):at
android.app.ActivityThread.performLaunchActivity(ActivityThread.jav
a:2103)
E/AndroidRuntime( 583):... 11 more
which I take to mean we're not going to find out. :-)
So I'm going to try doing this all over again, more methodically, tomorrow
on my Linux box.
--
Faber Fedor
Cloud Computing New Jersey
http://cloudcomputingnj.com
--- BEGIN LOGCAT OUTPUT
D/AndroidRuntime( 583): Shutting down VM
W/dalvikvm( 583): threadid=3: thread exiting with uncaught exception
(group=0x40010e28)
E/AndroidRuntime( 583): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime( 583): java.lang.RuntimeException: Unable to start
activity
ComponentInfo{com.faberfedor.tagyourworld/com.faberfedor.tagyourworld.MainMap}:
java.lang.NullPointerException
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2140)
E/AndroidRuntime( 583): at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2156)
E/AndroidRuntime( 583): at
android.app.ActivityThread.access$1800(ActivityThread.java:112)
E/AndroidRuntime( 583): at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1580)
E/AndroidRuntime( 583): at
android.os.Handler.dispatchMessage(Handler.java:88)
E/AndroidRuntime( 583): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 583): at
android.app.ActivityThread.main(ActivityThread.java:3742)
E/AndroidRuntime( 583): at
java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 583): at
java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497)
E/AndroidRuntime( 583): at dalvik.system.NativeStart.main(Native
Method)
E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 583): at
org.apache.harmony.luni.util.FloatingPointParser.parseDouble(FloatingPointParser.java:254)
E/AndroidRuntime( 583): at
java.lang.Double.parseDouble(Double.java:332)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141)
E/AndroidRuntime( 583): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122)
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2103)
E/AndroidRuntime( 583): ... 11 more
I/Process ( 54): Sending signal. PID: 583 SIG: 3
I/dalvikvm( 583): threadid=7: reacting to signal 3
I/dalvikvm( 583): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 583): Sending signal. PID: 583 SIG: 9
I/ActivityManager( 54): Process com.faberfedor.tagyourworld (pid 583) has
died.
--- END LOGCAT OUTPUT
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't send private questions to me, as I don't have time to
provide private support. All such questions should be posted on public
forums, where I and others can see and answer them.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Changing package names fubars the map overlays?
Assume I'm a idio^H^H^H^Hn00b and explain it to me, please. I don't see
what you do.
On Tue, Jan 20, 2009 at 10:27 PM, Dianne Hackborn hack...@android.comwrote:
This is the cause as shown in the stack crawl:
E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 583): at org.apache.harmony.luni.util.
FloatingPointParser.parseDouble(FloatingPointParser.java:254)
E/AndroidRuntime( 583): at
java.lang.Double.parseDouble(Double.java:332)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141)
E/AndroidRuntime( 583): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122)
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(
On Tue, Jan 20, 2009 at 6:51 PM, Faber Fedor faberfe...@gmail.com wrote:
On Tue, Jan 20, 2009 at 9:11 PM, Mark Murphy mmur...@commonsware.comwrote:
That is probably the bottom of the stack trace. I'm interested in the
top.
I've pasted the output of logcat, trimmed beneath my sig. Unfortunately,
the top of the stack trace reads:
E/AndroidRuntime( 583):at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.ja
va:1122)
E/AndroidRuntime( 583):at
android.app.ActivityThread.performLaunchActivity(ActivityThread.jav
a:2103)
E/AndroidRuntime( 583):... 11 more
which I take to mean we're not going to find out. :-)
So I'm going to try doing this all over again, more methodically, tomorrow
on my Linux box.
--
Faber Fedor
Cloud Computing New Jersey
http://cloudcomputingnj.com
--- BEGIN LOGCAT OUTPUT
D/AndroidRuntime( 583): Shutting down VM
W/dalvikvm( 583): threadid=3: thread exiting with uncaught exception
(group=0x40010e28)
E/AndroidRuntime( 583): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime( 583): java.lang.RuntimeException: Unable to start
activity
ComponentInfo{com.faberfedor.tagyourworld/com.faberfedor.tagyourworld.MainMap}:
java.lang.NullPointerException
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2140)
E/AndroidRuntime( 583): at
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2156)
E/AndroidRuntime( 583): at
android.app.ActivityThread.access$1800(ActivityThread.java:112)
E/AndroidRuntime( 583): at
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1580)
E/AndroidRuntime( 583): at
android.os.Handler.dispatchMessage(Handler.java:88)
E/AndroidRuntime( 583): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 583): at
android.app.ActivityThread.main(ActivityThread.java:3742)
E/AndroidRuntime( 583): at
java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 583): at
java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AndroidRuntime( 583): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497)
E/AndroidRuntime( 583): at dalvik.system.NativeStart.main(Native
Method)
E/AndroidRuntime( 583): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 583): at
org.apache.harmony.luni.util.FloatingPointParser.parseDouble(FloatingPointParser.java:254)
E/AndroidRuntime( 583): at
java.lang.Double.parseDouble(Double.java:332)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap$SitesOverlay.init(MainMap.java:275)
E/AndroidRuntime( 583): at
com.faberfedor.tagyourworld.MainMap.onCreate(MainMap.java:141)
E/AndroidRuntime( 583): at
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1122)
E/AndroidRuntime( 583): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2103)
E/AndroidRuntime( 583): ... 11 more
I/Process ( 54): Sending signal. PID: 583 SIG: 3
I/dalvikvm( 583): threadid=7: reacting to signal 3
I/dalvikvm( 583): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 583): Sending signal. PID: 583 SIG: 9
I/ActivityManager( 54): Process com.faberfedor.tagyourworld (pid 583)
has died.
--- END LOGCAT OUTPUT
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't send private questions to me, as I don't have time to
provide private support. All such questions should be posted on public
forums, where I and others can see and answer them.
--
Faber Fedor
Cloud Computing New Jersey
http://cloudcomputingnj.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To
