Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: =?ISO-8859-1?Q?Sven_K=F6hler?= Newsgroups: comp.lang.java.programmer Subject: Re: Exceptions Date: Sun, 03 Mar 2013 01:16:04 +0100 Lines: 20 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de 8C4ZZ+9HI5SjUDVGyJje2QcYrwFOZ0WIghxG+De/mFMjPbjyiwTD9yVLDPOwuLp5lKX7uW9CtN Cancel-Lock: sha1:6JKcFPi6QTvuilYfcbSdK2X2Zwg= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130223 Thunderbird/17.0.3 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:22687 Am 02.03.2013 20:08, schrieb subhabangalore@gmail.com: > I am trying to learn now exceptions. I am looking for a list of > common exceptions in Java and how one may debug them. You should learn about checked and unchecked exception and the difference between them. Consider the following examples: FileNotFoundException (checked) ArrayIndexOutOfBoundsException (unchecked) If by debugging an exception you mean to find its cause? Well, each exception has a stack trace and a message attached. That should tell you what happened, and where it happened. Not every exception needs debugging. A FileNotFoundException is perfectly normal, if one tries to open a file that does not exist. Regards, Sven