variables in scopes

[Frank Ch. Eigler]

Hi -

> [...]  Seriously, I believe that this is a fundamental safety We
> presumably won't crash any spacecraft, but we could crash a
> customer's system.  Dtrace doesn't have to worry about this so much
> because the user is in a pretty tight straitjacket.

Please be more specific.  Having implicitly declared and typed
systemtap variables poses a crash risk to the kernel how?


> > [...]
> > It seems to me that we are really missing only a few constructs:
> > - referring to variables in target space
> > - performing -> . [] on those pointer variables and related names
> > Does something else very useful come to mind?
> 
> & lvalue
> * pointer
> functions calls -- to three types of functions:
> a) SystemTap auxiliary functions (as currently parsed)
> b) C functions in the context of the probed function
> c) C functions (set off by yacc/lex escapes such as %% or %{...%}) that
> are copied from the .stp file to the module's .c file.

That looks like way too generous.  Can you provide motivation for each
of these constructs as really useful/necessary to a systemtap user?
They clearly toss the barn door wide open.


- FChE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/systemtap/attachments/20050414/1aea793f/attachment.sig>