RFR: 8364: Fix JULONG handling to set stackdepth value

[Martin Skarsaune]

On Tue, 4 Mar 2025 09:48:09 GMT, Hélios GILLES <duke at openjdk.org> wrote:

>> Fix JULONG handling to set stackdepth value
>> 
>> ---------
>> ### Progress
>> - [ ] Commit message must refer to an issue
>> - [ ] Change must be properly reviewed (1 review required, with at least 1 [Committer](https://openjdk.org/bylaws#committer))
>> 
>> ### Error
>>  ⚠️ The pull request body must not be empty.
>> 
>> ### Reviewing
>> <details><summary>Using <code>git</code></summary>
>> 
>> Checkout this PR locally: \
>> `$ git fetch https://git.openjdk.org/jmc.git pull/630/head:pull/630` \
>> `$ git checkout pull/630`
>> 
>> Update a local copy of the PR: \
>> `$ git checkout pull/630` \
>> `$ git pull https://git.openjdk.org/jmc.git pull/630/head`
>> 
>> </details>
>> <details><summary>Using Skara CLI tools</summary>
>> 
>> Checkout this PR locally: \
>> `$ git pr checkout 630`
>> 
>> View PR using the GUI difftool: \
>> `$ git pr show -t 630`
>> 
>> </details>
>> <details><summary>Using diff file</summary>
>> 
>> Download this PR as a diff file: \
>> <a href="https://git.openjdk.org/jmc/pull/630.diff">https://git.openjdk.org/jmc/pull/630.diff</a>
>> 
>> </details>
>
> @skarsaune Could you create an issue for that ?

@RoiSoleil : Hmm, could you provide some context? I have very limited experience in this area.

> Yes sorry ...
> 
> Without the patch i'm unable to modifiy this value and so modify the stackdepth of my JVM : 
> 
> https://i.ibb.co/dw1qNnw3/2025-03-06-15-39-51-JDK-Mission-Control.png

I see @RoiSoleil . Perhaps someone more experienced, such as @aptmac or @thegreystone are better suited to categorize and create an issue for it? Thanks

-------------

PR Comment: https://git.openjdk.org/jmc/pull/630#issuecomment-2704021504
PR Comment: https://git.openjdk.org/jmc/pull/630#issuecomment-2704077715