> I noticed that the org.h2.build.Build class (no Ant? no Maven?) never adds a
> "-g" option
No, it uses the default settings, which means the "line numbers" debug
info is available. In 99% of the cases this is enough.
> I had to edit the source of Build.java to supply a
> "-g" option so I could debug the server.
No, you don't need that: line numbers debug info that is present in
the default jar file is sufficient for debugging. You need to point
the IDE to the source jar file, which is available for download on
Maven, for example:
http://repo2.maven.org/maven2/com/h2database/h2/1.3.161/ -
h2-1.3.161-sources.jar
To analyze stack traces, you can also use the online "Error Analyzer":
http://h2database.com/html/sourceError.html
Regards,
Thomas
No, you don't need that: line numbers debug info that is present in
the default jar file is sufficient for debugging.
> I needed the variable values,
> which were not showing up in Netbeans 7 when it was pointed at the -sources
> jar (which I asked Netbeans to download, which it did successfully).
OK, in that case the easiest solution is probably to compile H2
yourself in the IDE.
The default H2 jar file includes line number debug info, this is very
helpful when analyzing exception stack traces, or when profiling.
I don't want to include variable debug info in the default jar files,
and providing additional jar files or build options would confuse
people more than help... Only very few people want to debug the
database engine itself, and those who do can compile H2 themselves in
the IDE, I think that's not too much to ask.
Regards,
Thomas
I don't want to include variable debug info in the default jar files,
and providing additional jar files or build options would confuse
people more than help... Only very few people want to debug the
database engine itself, and those who do can compile H2 themselves in
the IDE, I think that's not too much to ask.