[
https://issues.apache.org/jira/browse/NETBEANS-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190293#comment-17190293
]
Jerome Lelasseux commented on NETBEANS-4295:
--------------------------------------------
I had the same issue on Win10 with AdoptOpenJDK x64 11.0.8. It's SUPER annoying
when debugging exception from stack trace.
A dirty workaround which worked for me was to download AdoptOpenJDK 11.0.8 x86
and configure my Netbeans platform application to use it (note that the
Netbeans IDE still runs on x64).
> No console output when debugging platform on Windows
> ----------------------------------------------------
>
> Key: NETBEANS-4295
> URL: https://issues.apache.org/jira/browse/NETBEANS-4295
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Launchers&CLI
> Affects Versions: 9.0, 10.0, 11.0, 11.1, 11.2, 11.3
> Environment: Windows
> Reporter: Austin Stephens
> Priority: Major
> Labels: console, debug, output
>
> When you run Netbeans on a Mac or Linux, you can see the console output when
> debugging a Netbeans platform application, likely because they inherit std in
> and out. This does not happen on Windows. This makes it much harder to do
> debugging because operations (such as `Throwable.printStackTrace()`) produce
> no output in the output window.
> This can easily be reproduced by creating a new Netbeans Platform Application
> and debugging it. You will see logger output on Mac and Linux, but not in
> Windows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
