[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    JDK-8151815: Could not parse core image with JSnap.
From:       Yasumasa Suenaga <yasuenag () gmail ! com>
Date:       2017-06-13 5:10:14
Message-ID: CAGFVN2DU=5i6k3XU_C=q+swAvX-NxZJntpfC1WmsC_tA66j3qw () mail ! gmail ! com
[Download RAW message or body]

Hi all,

I want to discuss about JDK-8151815: Could not parse core image with JSnap.


In last year, I found JSnap cannot parse coredump and I've sent review
request for it as JDK-8151815. However it has not been reviewed yet
[1].

We've discussed about safety implementation, but we could not get consensus.
IMHO all SA tools should be handled java processes and core images,
and PerfCounter value is useful. So I fix this issue.

I uploaded new webrev for this issue. I think this patch is safety
because new flag PerfMemory::_destroyed guards double free, and all
members in PerfMemory is accessible (they are not munmap'ed)

  http://cr.openjdk.java.net/~ysuenaga/JDK-8151815/webrev.03/


Can you cooperate?


Thanks,

Yasumasa


[1] http://mail.openjdk.java.net/pipermail/serviceability-dev/2016-April/019480.html
[prev in list] [next in list] [prev in thread] [next in thread]