RFR: 8197429: Increased stack guard causes segfaults on x86-32

[Leonid Mesnik]

Could you please verify that expected libs are generated in test-mage directory
<jdk-root>/build/linux-x64/images/test/hotspot/jtreg/native. This directory contains all native binaries used during hotspot testing.

Also you need to add 
 -nativepath:<path-to-test-image>
like
-nativepath:<jdk-root>/build/linux-x64/images/test/hotspot/jtreg/native
in your jtreg command-line. So jtreg set correct library path for tested jdk.

Please check if it helps to run test correctly.

Leonid

> On Feb 12, 2018, at 6:29 AM, Andrew Haley <aph at redhat.com> wrote:
> 
> On 10/02/18 00:41, Leonid Mesnik wrote:
>> 4) Currently the correct way to use native libs is to compile it during build and use with -nativepath. 
>> See make examples here:
>> http://hg.openjdk.java.net/jdk/jdk10/file/tip/make/test/JtregNativeHotspot.gmk
>> <http://hg.openjdk.java.net/jdk/jdk10/file/tip/make/test/JtregNativeHotspot.gmk>http://hg.openjdk.java.net/jdk/jdk10/file/tip/test/hotspot/jtreg/runtime/jni/CalleeSavedRegisters <http://hg.openjdk.java.net/jdk/jdk10/file/tip/test/hotspot/jtreg/runtime/jni/CalleeSavedRegisters>
>> So you might rewrite your test completely on java. So you could use requires tag to filter out unsupported platforms.
>> Also logic of choosing platform will be slightly different. 
> 
> I've done this, but I've been unable to figure out how to run the
> test.  There are many places containing instructions, and all of them
> seem to be out of date.  My usual technique of running jtreg from the
> command line doesn't work.  I'd be very grateful if you could tell me
> the correct incantation to run a single jtreg test form the command
> line.  Thank you.
> 
> -- 
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671