similar to: Building ustack() helpers on OS X without -G

I cannot seem to probe any of the Python interpreter''s C functions on OS X. $ sudo dtrace -n ''pid$target::PyEval_EvalFrameEx:entry'' -c python dtrace: invalid probe specifier pid$target::PyEval_EvalFrameEx:entry: probe description pid59706::PyEval_EvalFrameEx:entry does not match any probes These functions show up in ustack()s, but they do not appear to be available

I have a test program which has a call sequence of a(), b(), c(), d(). When I place a pid return probe on d(), I get a ustack that looks like this: a.out`d+0x19 a.out`b+0xd a.out`a+0xd a.out`main+0x3c a.out`_start+0x7a The c() method appears to be missing. I did some poking around and noticed that pid return probes

I''m trying to time a function within Firefoxwith a pid$target probe [2]. e.g dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 13954 -s menu- construct.d -s sigcont.d elapsed: 12.7942481ms cpu : 7.7911194ms count : 40 times I''m also measuring Firefox startup time by running it arguments like this: ... file:///Users/joelr/work/mozilla/startup/startup.html#`python

Howdy, I was playing around with the malloc/free D script provided by Philip Beevers: http://www.opensolaris.org/jive/thread.jspa?threadID=4224&tstart=15 And decided to change the free:entry probe from: pid24169::free:entry / sz[arg0] / { printf("Freeing %p (size %d)\n", arg0, sz[arg0]); sz[arg0] = 0; } to: pid24169::free:entry / ! sz[arg0] / { printf("[ *

Hi people, When working with some usdt C++ probes we have come across a few issues. Controlling USDT Function name: Putting in usdt probes into C++ code gives you the mangled enclosing function name for the probes Function name. Working around this can be a pain. You need to wrap your usdt probes in extern C functions and call these. Could we have an option to control the Function name for

I have been doing some profiling using the profile provider. I have a command that runs more slowly on the T1000 than it does on prior systems and I am trying to find out why. Using the profile provider at 1000 hz, and aggregating on the ustack output, I find that the same function appears at the top of the stack on both platforms, but on each there are specific instruction locations within

Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {

Hello, The Hotspot JVM Runtime group would like to put forth a project proposal to improve the capabilities of DTrace''s ustack()/jstack() actions to better handle non-standard user stack frames. This email will describe the background, the problem, and our proposed solution. We''re interested in getting a sponsor for this work to help us with the process of getting the

I'm only doing one frame using speex_encode_int greatly simplifies my code I'm not sure why the sample I was working off of was converting the shorts to floats then calling the other encode/decode methods. Based off of your suggestions I tried the following but I get the same result. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) {

Alright noted, I changed me code so that the state is created in the constructor and destroyed in the destructor of the object. However I'm still getting the same issue although I'm sure that would have bit me sooner or later. The new code is as follows. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) { short *in=(short*)inputBuffer;

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | [root@enigma 0 3]$ rpcclient enigma -U 'root%XXXXXXXXXX' -c 'enumdrivers' | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | [root@enigma 0 3]$ rpcclient enigma -U

Hi Ryan, > Does anyone happen to know why the ustack() doesn''t show lex, > yak, main > and _start? A quick look with the source browser seems to indicate that _rt_boot is code executed very early in the lifetime of your process by ld.so.1. What seems to be happening is that ld.so.1 has allocated some memory before DTrace got control of your process - long before main() was

I'm completely new to speex and I'm having issues adding it to my application. I can pass raw PCM and that works fine so I know my transmission code is fine however when I try to encode/decode using speex I get noise almost like a whining/buzzing sound. I'm sure it's and issue in my code but I'm not sure where to start looking other then my gut tells me I'm not sizing or

As of patch 32953 dtrace support is in bleadperl (5.11.0). The probes are based on Alan Burlinson''s original blog post on the subject: http://blogs.sun.com/alanbur/date/20050909 By guarding the probes with PERL_SUB_*_ENABLED the performance hit is unmeasurable. All the necessary bits already existed in the wild. I just assembled them and made the necessary changes to

Parameters are: Samba 2.2.7a PDC setup with LDAP includeing posix authentication for Linux. OK, the tutorial I've based my setup on is the Mandrake tutorial found at http://www.mandrakesecure.net/en/docs/ldap-auth.php Works great for autenticateing Linux from LDAP but it is really sparse on the Samba side of things. Esepcially when it comes to adding machine trust accounts. So anyway I

Hi, I am fairly new to DTrace, and wanted to ask something regarding synchronization objects. I have a multithreaded C++ program in which I use semaphores (POSIX version) for synchronization. I was interested in using DTrace to figure out the total time for which each thread in my application sleeps, blocked on a semaphore, i.e., as a result of sem_wait() call. In order to measure this, I

I have a funny issue whereby when a application exits the proc:::exit probe doesn''t seem to be firing. A customer has written a dtrace script that outputs some info whenever proc:::exit fires but on occasion (random, no pattern in behaviour) dtrace exits without outputting the data. They are running dtrace via ''dtrace -s exit_trace.d -p <pid>'' Can anyone think

Hello. I have made a ogv file for testing html5 video using ffmpeg2theora for Windows. It is available on http://wwsi.edu.pl/video/enigma.html and http://movies.wwsi.edu.pl/wwsi/small/enigma.ogv . It looks it works fine in Firefox, Opera for Windows, VLC, mplayer, ffmpegplay, some other Linux browsers. It fails in Chrome (and Chromium), the video looks very out of synchronization. I

Being a responsible sort of guy, I want to check and make sure I have some decent encryption settings for my authentication systems. Namely Samba PDC (2.2.7a) with an LDAP backend that also authenticates Linux clients (which I've finally gotten running the way I want :-)). According to some documentation I've found, the samba ports are 137/udp,138/udp and 139/tcp. Samba changes

How do I query an application to see if it supports any USDT probe points?