david bone
2008-Jan-30 02:31 UTC
[dtrace-discuss] Fwd: Help on refining pid probe in a multi-threaded process
This is the 2nd email regarding subject in response to Adam. I hope it helps the community in my ramblings to solve a tough problem. Thk u Adam for the ongoing dialogue. Dave Begin forwarded message:> From: david bone <bone_david at mac.com> > Date: January 28, 2008 8:15:41 PM EST (CA) > To: Adam Leventhal <ahl at eng.sun.com> > Subject: Re: [dtrace-discuss] Help on refining pid probe in a multi- > threaded process > > Hi Adam, > I''ve attached 3 files: > 1) o2debug1.d --- dtrace file showing my pid function traces and > its companion `4.log` file showing the output. I''ve commented > inside the `d` file my objectives and observations. The `4.log` > file shows the threads spawned etc but no tracing of their functions. > 2) o2debug2.d --- trying to set probe firing using absolute > addressing. the `d` file has comments and the Dtrace compiler''s > error messages. > > I''m running on a Sun Ultra m20(2 cpued) AMD64bit work station > Solaris 10. > > I thank u for your time.??? > Dave > > On 25-Jan-08, at 11:15 AM, Adam Leventhal wrote: > >> Hi Dave, >> >>> 1) how do i set an absolute address probe in a pid provider of C++ >>> code? i figured out how to set a C++ function probe by using the >>> mangled name. i get a compiler error on my attempt at an absolute >>> address declaration in my attempts to figure out how to declare it. >>> The address is part of the process space and not specific to eg >>> `main`. >> >> What are you trying and what''s the error you''re seeing? >> >>> 2) can i declare multithreaded probes so that i can observe the >>> specific probe firings per declared thread? >> >> I''m not sure exactly what you mean, but you can record your thread >> ID when >> a probe fires using the ''tid'' variable. >> >>> 2.1) how do i set pid probes against future threads? how do i >>> declare >>> each thread''s run context in the provider''s part for the potential >>> probe. these threads are not static but created and launched >>> depending on the runtime context. >>> 2.2) how do i get pid functions firing on these future threads? >> >> All threads in your process will be traced by the pid provider. >> >> Adam >> >> -- >> Adam Leventhal, Fishworks http:// >> blogs.sun.com/ahl >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080129/8e109595/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: o2debug2.d Type: application/octet-stream Size: 3192 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080129/8e109595/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: 4.log Type: application/octet-stream Size: 196855 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080129/8e109595/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: o2debug1.d Type: application/octet-stream Size: 2617 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080129/8e109595/attachment-0002.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080129/8e109595/attachment-0001.html>