On Wed, 28 Sep 2022 14:43:43 GMT, Patricio Chilano Mateo
wrote:
>> Please review this small fix in async_get_stack_trace(). The GrowableArrays
>> created to store the bci and Method* of each frame found while traversing
>> the stack are allocated in the resource area of the thread that calls
> Please review this small fix in async_get_stack_trace(). The GrowableArrays
> created to store the bci and Method* of each frame found while traversing the
> stack are allocated in the resource area of the thread that calls
> async_get_stack_trace(). But if the handshake is executed by the tar
On Mon, 26 Sep 2022 14:23:38 GMT, Patricio Chilano Mateo
wrote:
> Please review this small fix in async_get_stack_trace(). The GrowableArrays
> created to store the bci and Method* of each frame found while traversing the
> stack are allocated in the resource area of the thread that calls
> a
On Mon, 26 Sep 2022 14:23:38 GMT, Patricio Chilano Mateo
wrote:
> Please review this small fix in async_get_stack_trace(). The GrowableArrays
> created to store the bci and Method* of each frame found while traversing the
> stack are allocated in the resource area of the thread that calls
> a
On Tue, 27 Sep 2022 16:09:07 GMT, Patricio Chilano Mateo
wrote:
>> src/hotspot/share/classfile/javaClasses.cpp line 2004:
>>
>>> 2002: const bool skip_hidden = !ShowHiddenFrames;
>>> 2003:
>>> 2004: // Pick some initial length
>>
>> The comment should at least hint at there being
On Tue, 27 Sep 2022 06:48:50 GMT, David Holmes wrote:
> Good find! Looks good! A couple of queries at this stage.
>
> Thanks.
>
Thanks for looking at this David.
> src/hotspot/share/classfile/javaClasses.cpp line 2004:
>
>> 2002: const bool skip_hidden = !ShowHiddenFrames;
>> 2003:
>> 2
On Mon, 26 Sep 2022 14:23:38 GMT, Patricio Chilano Mateo
wrote:
> Please review this small fix in async_get_stack_trace(). The GrowableArrays
> created to store the bci and Method* of each frame found while traversing the
> stack are allocated in the resource area of the thread that calls
> a
