Hi!
On Sep 16, 2007, at 10:29 PM, James C. McPherson wrote:
Are you approaching this with the use of SDT probes,
and which DTrace file are you referring to when you
write "The Dtrace file isn't built" ?
Yes. I've got a set of SDT probes done for the core of mysqld done.
What I am now looking at is how we can handle the vendors storage
engines. The engines can be either dynamically or statically compiled
into the server. From what I gather we are going to have to change
our builds for Solaris to make all engines dynamically compiled in
order to make them visible (aka probes in a library such as
ha_innodb.a are not going to work).
The skeleton is an example we give to vendors, and we are nearing our
5.1 release (so I am trying to get this done quickly enough so that
some of the vendors will have an example of what to do).
What sort of probes are you defining in skeleton_probes?
Have you tried to #ifdef around the Solaris-specific
definitions and inclusions?
Yes. I can do that with:
if BUILD_DTRACE
libskeleton_engine_la_SOURCES += skeleton_probes.d
endif
We still need to include the output from dtrace -h -s
skeleton_probes.d, but fixing the Windows compatibility issue was
simple enough.
The big problem is, the engines/assorted libraries are built with
libtool. I'm not having much luck sorting out how to make dtrace work
with this setup. We have dtrace working for the core, but it would be
nice to instrument the engines as well.
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
http://exploitseattle.com/ <-- Fun
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
dtrace-discuss mailing list
[email protected]
