dtrace discuss - Feb 2008 - Why dtrace doesn''t work on some workstation?

Dtrace does work on some workstation, such as as follows,

-----------------------------------------------------------
bash-3.00# dtrace -s ./mem.d `pgrep test`
dtrace: script ''./mem.d'' matched 5 probes
^C

bash-3.00# uname -a
SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100

bash-3.00# dtrace -V
dtrace: Sun D 1.1

---------------------------------------------------------

But it doesn''t work on some workstations, as follows

---------------------------------------------------------

bash-3.00# dtrace -s ./mem.d `pgrep test`
dtrace: failed to compile script ./mem.d: line 3: probe description
pid6852:libmtmalloc.so.1:malloc:entry does not match any probes

bash-3.00# dtrace -V
dtrace: Sun D 1.3

bash-3.00# uname -a
SunOS ftp1_oam 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V210

---------------------------------------------------------

Is there some problems in Dtrace version 1.3 ?

BRs/JianLi


--
This message posted from opensolaris.org

Is ''test'' a short lived process by any chance ?
2ndly could you please run ''pldd''  on process
''test'' and confirm that
libmtmalloc is in use on both the systems ?

LiJIan wrote:
> Dtrace does work on some workstation, such as as follows,
>
> -----------------------------------------------------------
> bash-3.00# dtrace -s ./mem.d `pgrep test`
> dtrace: script ''./mem.d'' matched 5 probes
> ^C
>
> bash-3.00# uname -a
> SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100
>
> bash-3.00# dtrace -V
> dtrace: Sun D 1.1
>
> ---------------------------------------------------------
>
> But it doesn''t work on some workstations, as follows
>
> ---------------------------------------------------------
>
> bash-3.00# dtrace -s ./mem.d `pgrep test`
> dtrace: failed to compile script ./mem.d: line 3: probe description
pid6852:libmtmalloc.so.1:malloc:entry does not match any probes
>
> bash-3.00# dtrace -V
> dtrace: Sun D 1.3
>
> bash-3.00# uname -a
> SunOS ftp1_oam 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V210
>
> ---------------------------------------------------------
>
> Is there some problems in Dtrace version 1.3 ?
>
> BRs/JianLi
>
>
> --
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
>

I used "ldd" to see the libraray linked, result shows libmtmalloc.so.1
is linked correctly.

Strange thing is if I start dtrace script at the same time runing the programme
i.e. using "dtrace -qs ./mem.d -c ./test",
libmtmalloc.so.1:malloc:entry can be found. I don''t know the difference
between the two ways.

Although "target" way  (run script at the same run programme) works,
but because when program starts up there are many memory allocation which will
not be released until the termination, I don''t want this way.

JianLi


--
This message posted from opensolaris.org

We''re going to need some more information to diagnose your problem.  
For example,
can you send the mem.d script? It''s actually important to use pldd  
rather than ldd
since pldd will actually show the libraries being used at runtime. Is  
this problem
always reproducible? Are you able to just enable that probe  
individually?

Adam

On Feb 26, 2008, at 8:09 PM, LiJIan wrote:
> I used "ldd" to see the libraray linked, result shows
libmtmalloc.so.
> 1 is linked correctly.
>
> Strange thing is if I start dtrace script at the same time runing  
> the programme i.e. using "dtrace -qs ./mem.d -c ./test",  
> libmtmalloc.so.1:malloc:entry can be found. I don''t know the  
> difference between the two ways.
>
> Although "target" way  (run script at the same run programme)
works,
> but because when program starts up there are many memory allocation  
> which will not be released until the termination, I don''t want
this
> way.
>
> JianLi
>
>
> --
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org

--
Adam Leventhal, Fishworks                        http://blogs.sun.com/ahl

You can also try LD_DEBUG and compare the output on different machines.

http://docs.sun.com/app/docs/doc/817-1984/chapter3-31?a=view

Rayson



On 2/26/08, LiJIan <lijianwhq at 163.com> wrote:
> I used "ldd" to see the libraray linked, result shows
libmtmalloc.so.1 is linked correctly.
>
> Strange thing is if I start dtrace script at the same time runing the
programme i.e. using "dtrace -qs ./mem.d -c ./test",
libmtmalloc.so.1:malloc:entry can be found. I don''t know the difference
between the two ways.
>
> Although "target" way  (run script at the same run programme)
works, but because when program starts up there are many memory allocation which
will not be released until the termination, I don''t want this way.
>
> JianLi
>
>
> --
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
>