> > > Spouting off ideas: perhaps tracerawmem()?
> >
> > You don't actually even need to do that -- this can be done purely in
> > terms of implementation changes. (We just need to break out tracemem()
> > as its own action type -- DTRACEACT_TRACEMEM -- and then act on that
> > accordingly at user-land. As Adam said, it's a good project for someone
> > to pick up who is interested in getting their feet wet with DTrace.)
>
> Bryan, you seem to be responsible engineer for long time ago closed CR ;)
>
> 4937796 trace() and tracemem() should provide option to force hex output
>
> I don't see any use for additional dtrace modifications. If you want to
> print string, use trace() or printf(). If you want to hexdump use
> tracemem() with rawbytes option.
Ah yes, right. You would think that I would remember this given that
I added it, but you'd be wrong. ;) Now the real question: why did I
do it this way instead of what seems to me (now) to be the better fix
of making tracemem() its own action? Would someone please offer to
put me under hypnosis so I can answer my own question? ;)
- Bryan
--------------------------------------------------------------------------
Bryan Cantrill, Sun Microsystems Fishworks. http://blogs.sun.com/bmc
_______________________________________________
dtrace-discuss mailing list
[email protected]
