I just noticed that if you put a commit in a clause after other actions, you get:
commit( ) may not follow data-recording action(s) But if you read this and then move the commit to earlier in the clause, you get: data-recording actions may not follow commit( ) So, two comments: 1. This is a case where a more general error message would probably have been more helpful than the more specific ones. 2. Why can't they be combined? If the data recording actions are not after a speculate, I don't even see how they are related. I could see if the commit went off into some other part of the dtrace code and the rest of the actions were not executed that having the commit be first would be a problem, but then a commit at the end should work. What is the reasoning here? -- blu There are two rules in life: Rule 1- Don't tell people everything you know ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom _______________________________________________ dtrace-discuss mailing list [email protected]
