I got the saem errors:
joshi{blu}128:; cat repl.d
#!/bin/sh
#include </usr/include/sys/utsname.h>
syscall::uname:entry
{
this->in = (struct utsname *)arg0;
}
syscall::uname:return
{
copyoutstr($$1, (uintptr_t)&this->in->release[0], SYS_NMLN);
}
joshi{blu}129:; repl.d
repl.d: syscall::uname:entry: not found
repl.d: syntax error at line 5: `(' unexpected
joshi{blu}130:; uname -a
SunOS joshi 5.11 onnv-gate:2007-07-05 sun4u sparc SUNW,Sun-Fire-280R
James Carlson wrote:
> Brian Utterback writes:
>> Something is going wrong with the exec of dtrace. The error you see
>> is what you get when you are running the Bourne shell and try
>> to execute the dtrace script as a shell script. Could you have
>> a typo in the #! line?
>
> Good call ... the error messages produced are somewhat similar to what
> one would see if this were run as a "bash" script.
>
>>> syscall::uname:entry: not found
>>> syntax error at line 5: `(' unexpected
>
> The actual errors from /usr/bin/bash that I get are:
>
> bash: syscall::uname:entry: command not found
> bash: /tmp/foo: line 5: syntax error near unexpected token `('
> bash: /tmp/foo: line 5: ` this->in = (struct utsname *)arg0;'
>
> I'm unable to locate a shell that produces results identical to those
> reported by the original submitter, though. (Tried sh, bash, zsh,
> ksh88, ksh93, tcsh, and csh.)
>
> Perhaps it's a custom and unusually broken shell ... ?
>
--
blu
You know something is wrong when the New England Patriots face stiffer
penalties for spying on innocent Americans than Dick Cheney and
George Bush. - Gov. Bill Richardson
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
_______________________________________________
opensolaris-discuss mailing list
[email protected]
