On Sun, Sep 21, 2008 at 9:29 AM, Cyril Plisko <[EMAIL PROTECTED]> wrote: > Hello ! > > I am helping some guys with migration to DTrace in their (quite big) > application. during the migration they hit very strange problem.
Cyril, Something you could try is running dtrace with the environment variable DTRACE_DEBUG set to 1. This will give you copious amounts of debugging data. (If you've never looked at this debugging data, try looking at it for something very simple, like "dtrace -n 'pid$target::main:entry' -c ls" to get a feel for what the output looks like.) The output you see when the application hangs is likely to be a good starting point for debugging this. > > > A number of times we've managed to crash the application when > terminated the dtrace with Ctrl-C. When this happened the stack always > showed the rtld_db_dlactivity at the top of the stack (see below). > DTrace currently uses breakpoints in a few places, rtld_db_activity being one of them. What's likely happening is that your dtrace invocation isn't cleaning up after itself when you kill it. The application hits the breakpoint and crashes. See http://bugs.opensolaris.org/view_bug.do?bug_id=6593259 and related bugs. (I'm currently working on this bug.) Chad _______________________________________________ dtrace-discuss mailing list [email protected]
