Mainly size. Generally if a developer is going to debug JavaFX to point
of wanting to look at local variables, it doesn't seem a stretch for
them to build JavaFX.
-- Kevin
On 7/17/2019 9:57 AM, Tom Schindl wrote:
so what is the reason to strip them (i guess it it size) it is extremely
painful to don't see local-variables, have parameter names, arg1,arg2, ... .
Tom
On 17.07.19 17:01, Kevin Rushforth wrote:
When you say that don't see a problem, what exactly do you mean? If you
are able to see the local variables in a production build, then that
would in fact be surprising. The production builds, including EA builds,
should be being built with "-PCONF=Release" which would exclude vars.
Someone from Gluon should confirm.
-- Kevin
On 7/17/2019 7:56 AM, Michael Paus wrote:
Hi,
I don't see any problem of that kind with Eclipse, on MacOS, JavaFX
13-ea 9 via Maven.
Michael
Am 17.07.19 um 16:45 schrieb Kevin Rushforth:
That should have been enough to enable local variable symbols. We
have the following logic for JavaCompile tasks:
compile.options.debugOptions.debugLevel = IS_DEBUG_JAVA ?
"source,lines,vars" : "source,lines"
IS_DEBUG_JAVA is true if CONF is either Debug or DebugNative.
Maybe something else is stripping out the symbols.
Has anyone else debugged JavaFX recently and tried to look at local
vars? If not, I'll take a quick look later today.
-- Kevin
On 7/17/2019 7:38 AM, Robert Lichtenberger wrote:
I'm trying to get to the bottom of some weird layout problems in my
application.
To that end I want/need to debug JavaFX classes.
But when I step into JavaFX classes I don't see local variables or
parameter names.
So I thought debug symbols are probably stripped from the official
builds.
I rolled my own and tried
CONF = Debug
and
CONF = DebugNative
in gradle.properties, recompiled OpenJFX and integrated the libraries
into a little eclipse testproject.
But I still don't see parameter names or local variables.
Is there something else I need to do in order to see them?
Best regards,
Robert
