Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84791 invoked from network); 16 May 2008 16:18:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 May 2008 16:18:20 -0000 Received: (qmail 75063 invoked by uid 500); 16 May 2008 16:18:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 75034 invoked by uid 500); 16 May 2008 16:18:20 -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 75020 invoked by uid 99); 16 May 2008 16:18:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2008 09:18:20 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2008 16:17:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id ACC9F234C118 for ; Fri, 16 May 2008 09:17:55 -0700 (PDT) Message-ID: <829319018.1210954675706.JavaMail.jira@brutus> Date: Fri, 16 May 2008 09:17:55 -0700 (PDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3618) Perform thread dump with ASSERTS with jdk 1.5 or higher In-Reply-To: <337116952.1208203748626.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597524#action_12597524 ] Kathey Marsden commented on DERBY-3618: --------------------------------------- To start working with this, you can just use the following program. import org.apache.derby.shared.common.sanity.SanityManager; public class TestAssert { public static void main(String[] args) { SanityManager.ASSERT(true == false); } } It will just print the assertion to stdout. I still don't have a suggestion for automated testing to check the derby.log, but this at least will give you something to get started with. I think the easiest thing will be to add the stack traces to message in AssertFailure before calling super(message). Kathey > Perform thread dump with ASSERTS with jdk 1.5 or higher > ------------------------------------------------------- > > Key: DERBY-3618 > URL: https://issues.apache.org/jira/browse/DERBY-3618 > Project: Derby > Issue Type: Improvement > Components: Services > Affects Versions: 10.5.0.0 > Reporter: Kathey Marsden > Assignee: Erlend Birkenes > Priority: Minor > > It would be good to have a stack traces for all threads dump to the derby.log when an assertion occurs with JVM's that support it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.