Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 53861 invoked from network); 11 Jun 2007 23:07:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jun 2007 23:07:25 -0000 Received: (qmail 41869 invoked by uid 500); 11 Jun 2007 23:07:28 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 41647 invoked by uid 500); 11 Jun 2007 23:07:27 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 41638 invoked by uid 99); 11 Jun 2007 23:07:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2007 16:07:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2007 16:07:23 -0700 Received: from d1-emea-10.sun.com ([192.18.2.120]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l5BN6vjU001510 for ; Mon, 11 Jun 2007 23:06:59 GMT Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JJH00J01UQWB200@d1-emea-10.sun.com> (original mail from Dag.Wanvik@Sun.COM) for derby-dev@db.apache.org; Tue, 12 Jun 2007 00:06:57 +0100 (BST) Received: from khepri05.norway.sun.com ([129.159.112.194]) by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JJH001U4UVKHF00@d1-emea-10.sun.com> for derby-dev@db.apache.org; Tue, 12 Jun 2007 00:06:57 +0100 (BST) Date: Tue, 12 Jun 2007 01:06:55 +0200 From: Dag.Wanvik@Sun.COM (Dag H. Wanvik) Subject: Re: Derby developing, how to do debug. In-reply-to: Sender: Dag.Wanvik@Sun.COM To: derby-dev@db.apache.org Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT References: <466DACAB.5050302@mail.telepac.pt> User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.0.50 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Knut Magne Solem writes: > I forgot one thing.. I had some trouble to get debugging to work > properly in Eclipse with the 10.2.2.0 distribution on > http://db.apache.org/derby/derby_downloads.html. After some > troubleshooting i solved it by compiling Derby after enabling > debugging in ant.properties and adding debuglevel="lines,vars,source" > in all the build.xml in the source tree. Is it supposed to be that > hard or could I do it differently? Check out http://wiki.apache.org/db-derby/BuildingDerby if you didn't already for setting up Derby with Netbeans or Eclipse. I have the following properties set in my ~/ant.properties file (Unix, Linux), and can debug with Netbeans, for example, to step through source and view variables etc. : sane=true debug=true I think the last line is supposed to be unnecessary, but I added it once because I didn't get line info for some parts of the code (forget where) - maybe that has been fixed now. Caveat: In Netbeans, make sure the check boxes in Sources pane in the debugger are set for Derby source code - if not, you will not be able to step in the Derby code. Sometimes I use plain jdb, Emacs/jdee, or jswat as well for the small peak. And don't forget that println is still your friend ;) And Thread.dumpStack() can be a quick way to figure out where a method is called from.. ;) Good luck! Dag