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

List:       openjdk-serviceability-dev
Subject:    Re: Dtrace on macosx?
From:       David Holmes <david.holmes () oracle ! com>
Date:       2015-11-12 5:51:47
Message-ID: 564428F3.4040008 () oracle ! com
[Download RAW message or body]

On 12/11/2015 10:21 AM, serguei.spitsyn@oracle.com wrote:
> Hi Magnus,
>
> I'll try to provide the details I know.
> The libjvm_db is to support Solaris pstack utility that prints mixed
> java+native stacks.
> It can be potentially used on Linux and Mac OS X for the same purpose
> but needs an implementation in the OS.
>
> The generation of the JVM offsets headers on Solaris is used for both
> jhelper.d and libjvm_db.
> The jhelper.d is the dtrace helper supporting the jstack action that
> prints mixed
> java+native stacks like the pstack utility does.
> The dtrace jstack action has not been implemented yet on both Linux and
> MAC OS X.
> I have no information about any plans to implement it in the future.
> We keep this code in a hope it will be implemented at some point.
>
> My guess is that the hotspot.h, hotspot_jni.h and hs_private.h are still
> useful
> as they support the hotspot probes that should work on Linux and Mac OS X.
>
> I hope, someone else can comment on this as well.
> David H. may have some knowledge. :)

I have the same guess - the headers support this:

https://wiki.openjdk.java.net/display/MacOSXPort/Mac+OS+X+Port+Using+HotSpot+DTrace+Probes

but don't know for sure.

David H. :)


> Thanks,
> Serguei
>
>
> On 11/11/15 10:57, Magnus Ihse Bursie wrote:
>> Hi,
>>
>> In the hotspot build conversion project, I've started to analyze the
>> dtrace build on macosx. From what I can understand, the only thing
>> that are done on macosx is the dtrace_gen_headers target in
>> dtrace.make, which creates hotspot.h, hotspot_jni.h and hs_private.h.
>> No libraries seems to be build, so most of dtrace.make in bsd is dead
>> code. The comment
>> # Bsd does not build libjvm_db, does not compile on macosx
>> # disabled in build: rule in vm.make
>> has been there since the initial integration of the macosx port.
>>
>> My question is: are the generated headers still useful on their own?
>> Or are they just remnants of an old but ultimately failed effort to
>> get dtrace working on macosx?
>>
>> /Magnus
>
[prev in list] [next in list] [prev in thread] [next in thread]