db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3618) Perform thread dump with ASSERTS with jdk 1.5 or higher
Date Fri, 16 May 2008 16:17:55 GMT

    [ 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).


> 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:
>            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.

View raw message