William James wrote:
[CC:'ing summerofcode at opensolaris.org]
> On 3/11/07, Rayson Ho <rayrayson at gmail.com> wrote:
> > On 3/11/07, Michael Shapiro <mws at zion.eng.sun.com> wrote:
> > > A useful community
> > > project would be CTF extensions or pluggable libraries for Sun and GNU
> > > tools to provide access to line number data from the various compilers.
> >
> > How about a Google Summer of Code project??
>
> I'd rather go for the GSC project to add Dtrace probes to ksh93 but I
> don't know the ksh93 sources that well and need help.
I am currently trying to figure out how the "Google Summer Of Code"
stuff works.
The complexity/difficulty of getting DTrace probes implemented depends
on the type of probe. AFAIK the degree of difficulty looks like this
("1"=easy, "10"=godlike knowledge of universe required):
1. "xtrace" probe (just prints what the "xtrace" mode of the shell would
print)
2. Trace subprocess creation and exit (e.g. fork())
3. Trace subshell creation and destruction (subshell!=child process in
ksh93)
4. Trace shell function calls
5. Trace calls to external commands and builtin commands
6. Get stacktrace of running shell (e.g. in which shell function or
builtin command ksh93 is currently running in)
9. Track the creation/destruction of shell functions
10. Trace get/set/unset of all variables (AFAIK very hard (assuming we
want to track both set/get/unset from shell level and all ways of
internal set/get/unset+libshell's API) since there is no central place
within libshell to trace this - partially C functions, macros or direct
access is used for this)
AFAIK anything from [1]-[5] is good for a "Google Summer Of Code"
project but anything with a higher degree of difficulty may be too
much...
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
