Issue with Catch Handler

by Johnny Molina » Fri, 22 Oct 2010 05:31:56 GMT


Sponsored Links
 Hello,

I have recently hit a snag using the Android plugin to Eclipse. For
some reason, ALL of my errors being thrown don't initialize and show
me the error. Has anyone ever seen this issue before and if so, what
did you do to correct it?

In particular, I am seeing it when I try to invoke the HTTPGet in a
HTTPClient object. If I have no connectivity, then I should get an
error. The Catch block does fire when this occurs...however, when I
check my general Exception object, the object is NULL (NULL Pointer).
Why would this happen if the catch is grabbing the exception?

My exceptions used to be working....and I was able to see the stack
trace. However, I can no longer see any stack trace regardless of the
Exception class I am using. Can someone please help me understand what
the heck is wrong with Eclipse, Android, or both? Is there something I
am missing on the configuration side?...is this a bug?

Mind you, I have already used Stack Overflow for this question. It has
been viewed 40 times but no answer yet. I hope anybody on here can
help me understand why this is occurring.

Thanks in advance,

John

--



Issue with Catch Handler

by Brad Gies » Fri, 22 Oct 2010 08:22:50 GMT


 I have had the same problem... It's not the Exception that is null, it's 
that getMessage() returns null.


In some catch blocks (I think mainly or only to do with HTTPClient, but 
it may happen also with JSON Exceptions... I can't remember) calling 
e.getMessage() returns null since I updated my SDK to 2.2, and it caused 
major issues because I normally wrote that to a log file, which meant 
that my catch block was creating an exception....


Would love to know the reason... And would be even better if it got fixed.

In the meantime, I'm doing this in my catch block if I use the message 
for ANYTHING:


                String message = ex.getMessage();
                if (message == null)
                    message = "null";

Then I write the message... It's a major pain...

I don't have an answer for you either... just letting you know it's not 
just you :)


Sincerely,

Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
 http://bgies.com              http://nocrappyapps.com 
 http://bistroblurb.com        http://forcethetruth.com 
 http://ihottonight.com 
-----------------------------------------------------------------------
Everything in moderation, including abstinence (paraphrased)

Every person is born with a brain... Those who use it well are the successful 
happy ones - Brad Gies

Adversity can make or break you... It's your choice... Choose wisely - Brad Gies

Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead




Hello, I have recently hit a snag using the Android plugin to Eclipse. For some reason, ALL of my errors being thrown don't initialize and show me the error. Has anyone ever seen this issue before and if so, what did you do to correct it? In particular, I am seeing it when I try to invoke the HTTPGet in a HTTPClient object. If I have no connectivity, then I should get an error. The Catch block does fire when this occurs...however, when I check my general Exception object, the object is NULL (NULL Pointer). Why would this happen if the catch is grabbing the exception? My exceptions used to be working....and I was able to see the stack trace. However, I can no longer see any stack trace regardless of the Exception class I am using. Can someone please help me understand what the heck is wrong with Eclipse, Android, or both? Is there something I am missing on the configuration side?...is this a bug? Mind you, I have already used Stack Overflow for this question. It has been viewed 40 times but no answer yet. I hope anybody on here can help me understand why this is occurring. Thanks in advance, John
--


Sponsored Links


Issue with Catch Handler

by John Moline » Fri, 22 Oct 2010 10:58:40 GMT


 hanks Brad. I did narrow it down to my emulator. If I run the same
process without using the emulator, it runs fine. It looks like some
sort of permissions or framework issue within the emulator.

On Thu, Oct 21, 2010 at 7:22 PM, Brad Gies <rbg...@gmail.com> wrote:
>



Issue with Catch Handler

by DanH » Sat, 23 Oct 2010 01:44:50 GMT


  vaguely recall this being mentioned as a "feature" of the emulator.
Seems odd, though, since it should be easy to fix and it makes
debugging that much harder.

On Oct 21, 9:58pm, John Moline <molinesys...@gmail.com> wrote:
> >



Other Threads

1. A problem about application die unexpected.

I've met this problem serveral times.
When my application is running, some times it die unexpected. The
logcat print the message below:
(the application name is remove)

09-23 16:00:42.407: INFO/DEBUG(539): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
09-23 16:00:42.407: INFO/DEBUG(539): Build fingerprint: 'generic/sdk/
generic/:1.5/CUPCAKE/147336:eng/test-keys'
09-23 16:00:42.407: INFO/DEBUG(539): pid: 1471, tid: 1534  >>>
com.xx.xx <<<
09-23 16:00:42.407: INFO/DEBUG(539): signal 11 (SIGSEGV), fault addr
000000fe
09-23 16:00:42.407: INFO/DEBUG(539):  r0 ff9d9d9d  r1 43804000  r2
42320000  r3 45ba86a0
09-23 16:00:42.407: INFO/DEBUG(539):  r4 ff9d9d9d  r5 43804000  r6
becf511c  r7 45ba86e8
09-23 16:00:42.407: INFO/DEBUG(539):  r8 44da4008  r9 ffffff80  10
000074e7  fp 00000200
09-23 16:00:42.407: INFO/DEBUG(539):  ip ffffff81  sp 45ba8698  lr
ac043dfc  pc 000000fe  cpsr 90000030
09-23 16:00:42.467: INFO/DEBUG(539):          #00  pc 000000fe
09-23 16:00:42.548: INFO/DEBUG(539):          #01  pc 00043df8  /
system/lib/libsgl.so
09-23 16:00:42.557: INFO/DEBUG(539):          #02  pc 0003e018  /
system/lib/libsgl.so
09-23 16:00:42.557: INFO/DEBUG(539):          #03  pc 0004ea00  /
system/lib/libsgl.so
09-23 16:00:42.557: INFO/DEBUG(539):          #04  pc 00047e4c  /
system/lib/libsgl.so
09-23 16:00:42.568: INFO/DEBUG(539):          #05  pc 00075d64  /
system/lib/libsgl.so
09-23 16:00:42.568: INFO/DEBUG(539):          #06  pc 000767d4  /
system/lib/libsgl.so
09-23 16:00:42.568: INFO/DEBUG(539):          #07  pc 0005b3e8  /
system/lib/libsgl.so
09-23 16:00:42.578: INFO/DEBUG(539):          #08  pc 00054b80  /
system/lib/libsgl.so
09-23 16:00:42.578: INFO/DEBUG(539):          #09  pc 00052204  /
system/lib/libsgl.so
09-23 16:00:42.588: INFO/DEBUG(539):          #10  pc 0003d008  /
system/lib/libandroid_runtime.so
09-23 16:00:42.588: INFO/DEBUG(539):          #11  pc 0000e3b4  /
system/lib/libdvm.so
09-23 16:00:42.588: INFO/DEBUG(539): stack:
09-23 16:00:42.598: INFO/DEBUG(539):     45ba8658  00000000
09-23 16:00:42.598: INFO/DEBUG(539):     45ba865c  0000000b
09-23 16:00:42.611: INFO/DEBUG(539):     45ba8660  45ba86d4
09-23 16:00:42.611: INFO/DEBUG(539):     45ba8664  00000001
09-23 16:00:42.617: INFO/DEBUG(539):     45ba8668  00000010
09-23 16:00:42.632: INFO/DEBUG(539):     45ba866c  00000010
09-23 16:00:42.632: INFO/DEBUG(539):     45ba8670  00000010
09-23 16:00:42.632: INFO/DEBUG(539):     45ba8674  00000010
09-23 16:00:42.632: INFO/DEBUG(539):     45ba8678  44da4008
09-23 16:00:42.638: INFO/DEBUG(539):     45ba867c  00000080
09-23 16:00:42.638: INFO/DEBUG(539):     45ba8680  00000020
09-23 16:00:42.638: INFO/DEBUG(539):     45ba8684  45ba87ec
09-23 16:00:42.648: INFO/DEBUG(539):     45ba8688  00000006
09-23 16:00:42.648: INFO/DEBUG(539):     45ba868c  00000006
09-23 16:00:42.648: INFO/DEBUG(539):     45ba8690  df002777
09-23 16:00:42.648: INFO/DEBUG(539):     45ba8694  e3a070ad
09-23 16:00:42.648: INFO/DEBUG(539): #01 45ba8698  00000037
09-23 16:00:42.648: INFO/DEBUG(539):     45ba869c  00000000
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86a0  44da4008
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86a4  003039f0  [heap]
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86a8  45ba8b54
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86ac  00000080
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86b0  ffffffb7
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86b4  00000037
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86b8  00000100
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86bc  44da4008
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86c0  ffffff80
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86c4  becf511c  [stack]
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86c8  00000200
09-23 16:00:42.648: INFO/DEBUG(539):     45ba86cc  ac03e01c  /system/
lib/libsgl.so
09-23 16:00:43.577: INFO/ActivityManager(568): Process com.uc.browser
(pid 1471) has died.
09-23 16:00:43.599: INFO/WindowManager(568): WIN DEATH: Window
{43766f50 com.xx.xxr/com.xx.xx.Activityxx paused=false}
09-23 16:00:43.707: WARN/InputManagerService(568): Got RemoteException
sending setActive(false) notification to pid 1471 uid 10018

so, what happended? Is there any possible operation will cause this
problem?

--~--~---------~--~----~------------~-------~--~----~

2. Eclair feature list

Hi,

Donut has been official released, but eclair is still ongoing. I am
trying to get some official information about eclair, but has no
result. The following is what I got from internet, can anyone give me
more accurate information about eclair?

+Google Maps 4.0
+Chrome Sync
+Google Earth
+MultiTouch
+3D Enhancement
+Flash 10
+New Android Market

Many thanks!!!

CJ
--~--~---------~--~----~------------~-------~--~----~

3. Possible to send object via intent extras?

4. dblite file?

5. magic kalau jadi modem...?

6. Intent between 2 APK (different projects)?

7. need to build custom calendar