You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sean Bridges (Created) (JIRA)" <ji...@apache.org> on 2011/12/15 18:16:30 UTC
[jira] [Created] (DERBY-5543) include debug info in derby builds
uploaded to maven
include debug info in derby builds uploaded to maven
----------------------------------------------------
Key: DERBY-5543
URL: https://issues.apache.org/jira/browse/DERBY-5543
Project: Derby
Issue Type: Improvement
Components: Build tools
Affects Versions: 10.8.2.2
Reporter: Sean Bridges
Priority: Minor
Looking at a strack trace from derby retrieved through maven, I see that derby is compiled without debug information, this means line numbers are not available in stack traces,
Caused by: java.lang.NullPointerException
at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown Source)
at org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source)
at org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown Source)
at org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown Source)
and it is harder to debug code by setting breakpoints within derby. Derby deployed to maven should have debug information included.
I'm not sure how this is controlled, but looking at pom.xml I see,
<!-- Specifies whether to package the sane (debug) or insane jar.
Valid values: sane|insane
-->
<sanity>insane</sanity>
The default should be sane.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5543) include debug info in derby builds
uploaded to maven
Posted by "Dag H. Wanvik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170625#comment-13170625 ]
Dag H. Wanvik commented on DERBY-5543:
--------------------------------------
It could, but it would increase the jar files sizes (not the byte code), and thus possibly slow down class loading. I am not sure how large this effect is, though.
> include debug info in derby builds uploaded to maven
> ----------------------------------------------------
>
> Key: DERBY-5543
> URL: https://issues.apache.org/jira/browse/DERBY-5543
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2
> Reporter: Sean Bridges
> Priority: Minor
>
> Looking at a strack trace from derby retrieved through maven, I see that derby is compiled without debug information, this means line numbers are not available in stack traces,
> Caused by: java.lang.NullPointerException
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown Source)
> and it is harder to debug code by setting breakpoints within derby. Derby deployed to maven should have debug information included.
> I'm not sure how this is controlled, but looking at pom.xml I see,
> <!-- Specifies whether to package the sane (debug) or insane jar.
> Valid values: sane|insane
> -->
> <sanity>insane</sanity>
> The default should be sane.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5543) include debug info in derby builds
uploaded to maven
Posted by "Sean Bridges (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170583#comment-13170583 ]
Sean Bridges commented on DERBY-5543:
-------------------------------------
can the insane version have line numbers compiled into it?
> include debug info in derby builds uploaded to maven
> ----------------------------------------------------
>
> Key: DERBY-5543
> URL: https://issues.apache.org/jira/browse/DERBY-5543
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2
> Reporter: Sean Bridges
> Priority: Minor
>
> Looking at a strack trace from derby retrieved through maven, I see that derby is compiled without debug information, this means line numbers are not available in stack traces,
> Caused by: java.lang.NullPointerException
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown Source)
> and it is harder to debug code by setting breakpoints within derby. Derby deployed to maven should have debug information included.
> I'm not sure how this is controlled, but looking at pom.xml I see,
> <!-- Specifies whether to package the sane (debug) or insane jar.
> Valid values: sane|insane
> -->
> <sanity>insane</sanity>
> The default should be sane.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5543) include debug info in derby builds
uploaded to maven
Posted by "Sean Bridges (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170636#comment-13170636 ]
Sean Bridges commented on DERBY-5543:
-------------------------------------
I think the effect is pretty minor, disk is cheap and class loading only happens once. Most java libraries ship with line numbers and debug info included.
> include debug info in derby builds uploaded to maven
> ----------------------------------------------------
>
> Key: DERBY-5543
> URL: https://issues.apache.org/jira/browse/DERBY-5543
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2
> Reporter: Sean Bridges
> Priority: Minor
>
> Looking at a strack trace from derby retrieved through maven, I see that derby is compiled without debug information, this means line numbers are not available in stack traces,
> Caused by: java.lang.NullPointerException
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown Source)
> and it is harder to debug code by setting breakpoints within derby. Derby deployed to maven should have debug information included.
> I'm not sure how this is controlled, but looking at pom.xml I see,
> <!-- Specifies whether to package the sane (debug) or insane jar.
> Valid values: sane|insane
> -->
> <sanity>insane</sanity>
> The default should be sane.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5543) include debug info in derby builds
uploaded to maven
Posted by "Dag H. Wanvik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170580#comment-13170580 ]
Dag H. Wanvik commented on DERBY-5543:
--------------------------------------
I don't believe we want to make this the default download, since the "sane" version which has line numbers complied in also has other instrumentation enabled and is significantly slower. We could possibly install a debug version as well (with another name).
You can also download the debug jar files from the Apache site, of course, @ http://db.apache.org/derby/derby_downloads.html
> include debug info in derby builds uploaded to maven
> ----------------------------------------------------
>
> Key: DERBY-5543
> URL: https://issues.apache.org/jira/browse/DERBY-5543
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2
> Reporter: Sean Bridges
> Priority: Minor
>
> Looking at a strack trace from derby retrieved through maven, I see that derby is compiled without debug information, this means line numbers are not available in stack traces,
> Caused by: java.lang.NullPointerException
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.xact.Xact.openDroppedContainer(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.findpage(Unknown Source)
> at org.apache.derby.impl.store.raw.data.PageBasicOperation.needsRedo(Unknown Source)
> and it is harder to debug code by setting breakpoints within derby. Derby deployed to maven should have debug information included.
> I'm not sure how this is controlled, but looking at pom.xml I see,
> <!-- Specifies whether to package the sane (debug) or insane jar.
> Valid values: sane|insane
> -->
> <sanity>insane</sanity>
> The default should be sane.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira