On 01/25/16 00:18, STEVE wrote: > Hi Nan Xiao, > > Yes, it is unmount. Please see the man page below. I tried to run > unmount and dtrace both under root, same issue.
Just a nit, but the section 2 man page doesn't document the syscall interface. It documents the libc ABI. The two are different, and you can't always trust that one matches the other. A better place to look for supported syscall provider interfaces is here: dtrace -l -f syscall::\*mount\* or, if you prefer: dtrace -l -P syscall | grep mount At a guess, the problem is that the executable invoking unmount() itself was gone by the time the user-level dtrace got the information from the kernel. Since it seems you're looking for the user-level stack, I suggest enabling destructive actions and using stop() to halt the user process. It can then be examined with a debugger. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> ------------------------------------------- dtrace-discuss Archives: https://www.listbox.com/member/archive/184261/=now RSS Feed: https://www.listbox.com/member/archive/rss/184261/25769126-e243886f Modify Your Subscription: https://www.listbox.com/member/?member_id=25769126&id_secret=25769126-8d47a7b2 Powered by Listbox: http://www.listbox.com
