| compiler debug option on 3.4.2 [message #58343] |
Fri, 24 April 2009 12:52  |
Eclipse User |
|
|
|
hello,
Trying to get the debug info in our application code, using the
compilerArgs=-g option in our build.properties file
Problem is that some of our plugins in our application do have the debug
info (source and line numbers), but some others don't...
I tried looking in each plugin folder at build time, to get some more info.
each one has a build.xml file but they all look the same.
The content of that file is actually weird. The compilerArgs and other
properties show with the default values (<property name="compilerArg"
value=""/>) for both the plugins that end up with the debug info, and the
ones that don't.
Also, each plugin folder has a javaCompiler...args file created (which
seems to indicate the debug option is passed in properly...)
Any way to troubleshoot this and figure why some plugins are not compiled
with the debug option?
This issue is preventing us from doing proper remote debugging. we can set
break point in the plugin's code with the debug info, but not the other
ones....
Thanks,
|
|
|
| Re: compiler debug option on 3.4.2 [message #58366 is a reply to message #58343] |
Fri, 24 April 2009 16:18  |
| Eclipse User |
|
|
|
"compilerArg" is a top level build configuration property. It should be
set in the main builder's build.properties file.
There is also the "javacDebugInfo" property (whose values are "on" or
"off") which controls the debug attribute on the javac call.
Also if you set "logExtension=.xml" in the builder's build.properties
file, then the compiler should output xml files for logs, and the xml
files contain way more detail and might say something about debug info.
The top level build.properties file overrides anything you see in the
build.xml since ant properties don't change.
This might also be interesting to you:
http://aniefer.blogspot.com/2008/09/custom-compiler-argument s-in-pdebuild.html
-Andrew
Laurent Dubois wrote:
> hello,
>
> Trying to get the debug info in our application code, using the
> compilerArgs=-g option in our build.properties file
> Problem is that some of our plugins in our application do have the debug
> info (source and line numbers), but some others don't...
> I tried looking in each plugin folder at build time, to get some more info.
> each one has a build.xml file but they all look the same.
> The content of that file is actually weird. The compilerArgs and other
> properties show with the default values (<property name="compilerArg"
> value=""/>) for both the plugins that end up with the debug info, and
> the ones that don't.
> Also, each plugin folder has a javaCompiler...args file created (which
> seems to indicate the debug option is passed in properly...) Any way to
> troubleshoot this and figure why some plugins are not compiled with the
> debug option?
> This issue is preventing us from doing proper remote debugging. we can
> set break point in the plugin's code with the debug info, but not the
> other ones....
>
> Thanks,
>
|
|
|
| Re: compiler debug option on 3.4.2 [message #58409 is a reply to message #58366] |
Fri, 24 April 2009 16:49 |
| Eclipse User |
|
|
|
Thanks Andrew.
The compilerArgs is indeed set in the build.properties so that's why I was
a bit intrigued by the result...
Anyway, I managed to resolve the issue by running our build from the
command line as opposed to from the Eclipse IDE.
I still need to figure what's going on from the IDE but at least I got
something that I can use for remote debugging.
Thanks again...
|
|
|
| Re: compiler debug option on 3.4.2 [message #596381 is a reply to message #58343] |
Fri, 24 April 2009 16:18 |
| Eclipse User |
|
|
|
"compilerArg" is a top level build configuration property. It should be
set in the main builder's build.properties file.
There is also the "javacDebugInfo" property (whose values are "on" or
"off") which controls the debug attribute on the javac call.
Also if you set "logExtension=.xml" in the builder's build.properties
file, then the compiler should output xml files for logs, and the xml
files contain way more detail and might say something about debug info.
The top level build.properties file overrides anything you see in the
build.xml since ant properties don't change.
This might also be interesting to you:
http://aniefer.blogspot.com/2008/09/custom-compiler-argument s-in-pdebuild.html
-Andrew
Laurent Dubois wrote:
> hello,
>
> Trying to get the debug info in our application code, using the
> compilerArgs=-g option in our build.properties file
> Problem is that some of our plugins in our application do have the debug
> info (source and line numbers), but some others don't...
> I tried looking in each plugin folder at build time, to get some more info.
> each one has a build.xml file but they all look the same.
> The content of that file is actually weird. The compilerArgs and other
> properties show with the default values (<property name="compilerArg"
> value=""/>) for both the plugins that end up with the debug info, and
> the ones that don't.
> Also, each plugin folder has a javaCompiler...args file created (which
> seems to indicate the debug option is passed in properly...) Any way to
> troubleshoot this and figure why some plugins are not compiled with the
> debug option?
> This issue is preventing us from doing proper remote debugging. we can
> set break point in the plugin's code with the debug info, but not the
> other ones....
>
> Thanks,
>
|
|
|
| Re: compiler debug option on 3.4.2 [message #596394 is a reply to message #58366] |
Fri, 24 April 2009 16:49 |
| Eclipse User |
|
|
|
Thanks Andrew.
The compilerArgs is indeed set in the build.properties so that's why I was
a bit intrigued by the result...
Anyway, I managed to resolve the issue by running our build from the
command line as opposed to from the Eclipse IDE.
I still need to figure what's going on from the IDE but at least I got
something that I can use for remote debugging.
Thanks again...
|
|
|
Powered by
FUDForum. Page generated in 0.03521 seconds
Home