Re: RFR: 8242181: [Linux] Show source information when printing native stack traces in hs_err files [v9]

2022-06-07 Thread openjdk-notifier[bot] 
On Thu, 2 Jun 2022 11:29:58 GMT, Christian Hagedorn  
wrote:

>>> Thanks Thomas for doing the testing!
>> 
>> Hi Christian,
>> 
>> I can see no problems on ppcle attributable to your test. However, I may 
>> overlook something since tests are still failing all over the place because 
>> of loom.
>> 
>> I see test errors in TestDwarf on ppcle and x64, however. On x64:
>> 
>> 
>> --System.out:(52/5198)--
>> Command line: 
>> [/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/bin/java -cp 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_hotspot_tier1_work/JTwork/classes/runtime/ErrorHandling/TestDwarf.d:/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/grmpf/testdata/jtreg/jtreg_test_19/test/hotspot/jtreg/runtime/ErrorHandling:/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_hotspot_tier1_work/JTwork/classes:/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/grmpf/testdata/jtreg/jtreg_test_19/test/hotspot/jtreg:/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_hotspot_tier1_work/JTwork/classes/test/lib:/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/grmpf/testdata/jtreg/jtreg_test_19/test/lib:/net/sapmnt.sapjvm_work/openjdk/tools/jtreg-6+2/lib/javatest.jar:/net/sapmnt.sapjvm_work/openjdk/tools/jtreg-6+2/lib/jtreg.jar
>>  -Xmx768m -Djava.awt.headless=true 
>> -Djava.util.prefs.userRoot=/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_ho
 tspot_tier1_work/tmp 
-Djava.io.tmpdir=/priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_hotspot_tier1_work/tmp
 -Dtest.getfreeport.max.tries=40 -ea -esa -Xlog:dwarf=info 
-XX:-CreateCoredumpOnCrash -Xcomp -XX:CICrashAt=1 --version ]
>> [2022-05-24T18:37:00.974121691Z] Gathering output for process 44490
>> [2022-05-24T18:37:02.872100892Z] Waiting for completion for process 44490
>> [2022-05-24T18:37:02.872338192Z] Waiting for completion finished for process 
>> 44490
>> Output and diagnostic info for process 44490 was saved into 
>> 'pid-44490-output.log'
>> [2022-05-24T18:37:02.889455876Z] Waiting for completion for process 44490
>> [2022-05-24T18:37:02.889604189Z] Waiting for completion finished for process 
>> 44490
>> # To suppress the following error report, specify this argument
>> # after -XX: or in .hotspotrc:  SuppressErrorAt=/c1_Compilation.cpp:616
>> #
>> # A fatal error has been detected by the Java Runtime Environment:
>> #
>> #  Internal Error 
>> (/sapmnt/sapjvm_work/openjdk/nb/linuxx86_64/jdk-dev/src/hotspot/share/c1/c1_Compilation.cpp:616),
>>  pid=44490, tid=44505
>> #  assert(CICrashAt < 0 || (uintx)_env->compile_id() != (uintx)CICrashAt) 
>> failed: just as planned
>> #
>> # JRE version: OpenJDK Runtime Environment (19.0) (fastdebug build 
>> 19-internal-adhoc.openjdk.jdk-dev)
>> # Java VM: OpenJDK 64-Bit Server VM (fastdebug 
>> 19-internal-adhoc.openjdk.jdk-dev, compiled mode, sharing, tiered, 
>> compressed oops, compressed class ptrs, g1 gc, linux-amd64)
>> # Problematic frame:
>> # V  [libjvm.so+0x73ca34]  Compilation::~Compilation()+0x84
>> #
>> # CreateCoredumpOnCrash turned off, no core file dumped
>> #
>> # An error report file with more information is saved as:
>> # 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/jtreg_hotspot_tier1_work/JTwork/scratch/hs_err_pid44490.log
>> [1.835s][info][dwarf] Open DWARF file: 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/lib/server/libjvm.debuginfo
>> [1.842s][info][dwarf] Failed to parse the line number program header 
>> correctly.
>> [1.842s][info][dwarf] Failed to process the line number program correctly.
>> [1.842s][info][dwarf] Failed to retrieve file and line number information 
>> for 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/lib/server/libjvm.so
>>  at offset: 0x0074176a
>> [1.843s][info][dwarf] Failed to parse the line number program header 
>> correctly.
>> [1.843s][info][dwarf] Failed to process the line number program correctly.
>> [1.843s][info][dwarf] Failed to retrieve file and line number information 
>> for 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/lib/server/libjvm.so
>>  at offset: 0x00a05011
>> [1.845s][info][dwarf] Failed to parse the line number program header 
>> correctly.
>> [1.845s][info][dwarf] Failed to process the line number program correctly.
>> [1.845s][info][dwarf] Failed to retrieve file and line number information 
>> for 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/lib/server/libjvm.so
>>  at offset: 0x00a05b78
>> [1.849s][info][dwarf] Failed to parse the line number program header 
>> correctly.
>> [1.849s][info][dwarf] Failed to process the line number program correctly.
>> [1.849s][info][dwarf] Failed to retrieve file and line number information 
>> for 
>> /priv/jvmtests/output_openjdk19_dev_dbgU_linuxx86_64/sapjvm_19/lib/server/libjvm.so
>>  at offset: 0x018d49d3
>> [1.852s][info][dwarf] Failed to parse the line number program header 
>> correctly.
>> [1.852s][info][dwarf]

Re: RFR: 8274851: [PPC64] Port zgc to linux on ppc64le [v3]

2021-10-13 Thread openjdk-notifier[bot] 
On Fri, 8 Oct 2021 15:41:47 GMT, Niklas Radomski  wrote:

>> Port the Z garbage collector 
>> ([JDK-8209683](https://bugs.openjdk.java.net/browse/JDK-8209683)) to linux 
>> on ppc64le.
>
> Niklas Radomski has updated the pull request incrementally with three 
> additional commits since the last revision:
> 
>  - Remove superfluous copyright change
>  - Fix predicate conditions
>  - Add ByteSize constructor to Address

The dependent pull request has now been integrated, and the target branch of 
this pull request has been updated. This means that changes from the dependent 
pull request can start to show up as belonging to this pull request, which may 
be confusing for reviewers. To remedy this situation, simply merge the latest 
changes from the new target branch into this pull request by running commands 
similar to these in the local repository for your personal fork:


git checkout 8275049_ZGC_log_register
git fetch https://git.openjdk.java.net/jdk master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

-

PR: https://git.openjdk.java.net/jdk/pull/5842

Re: RFR: 8269760: idea.sh should not invoke cygpath directly

2021-07-05 Thread openjdk-notifier [bot] 
On Thu, 1 Jul 2021 14:54:04 GMT, Jorn Vernee  wrote:

> From the JBS issue:
> 
> Currently idea.sh checks if `CYGPATH` is set, and then continues by invoking 
> `cygpath` directly.
> 
> This doesn't work if `CYGPATH` is not actually set to `cygpath`, but to 
> something else, such as `wslpath`.
> 
> Instead of invoking `cygpath` directly, the value of the `CYGPATH` variable 
> should be used.

The dependent pull request has now been integrated, and the target branch of 
this pull request has been updated. This means that changes from the dependent 
pull request can start to show up as belonging to this pull request, which may 
be confusing for reviewers. To remedy this situation, simply merge the latest 
changes from the new target branch into this pull request by running commands 
similar to these in the local repository for your personal fork:


git checkout Idea_Conf
git fetch https://git.openjdk.java.net/jdk master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

-

PR: https://git.openjdk.java.net/jdk/pull/4655

Re: RFR: 8269761: idea.sh missing .exe suffix when invoking javac on WSL

2021-07-05 Thread openjdk-notifier [bot] 
On Thu, 1 Jul 2021 15:02:03 GMT, Jorn Vernee  wrote:

> From the JBS issue:
> 
> At the end, idea.sh tries to invoke javac, but when running on WSL this 
> results in the following error:
> 
> bin/idea.sh: line 249: /mnt/c/progra~1/java/jdk-16/bin/javac: No such 
> file or directory
> 
> Adding a .exe suffix to the javac path fixes this issue, which can be done 
> just for WSL.

The dependent pull request has now been integrated, and the target branch of 
this pull request has been updated. This means that changes from the dependent 
pull request can start to show up as belonging to this pull request, which may 
be confusing for reviewers. To remedy this situation, simply merge the latest 
changes from the new target branch into this pull request by running commands 
similar to these in the local repository for your personal fork:


git checkout Idea_Cygpath
git fetch https://git.openjdk.java.net/jdk master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

-

PR: https://git.openjdk.java.net/jdk/pull/4656