[Bug translator/6837] New: $$parms et al. should decode char *

["ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

Further to bug 5075, it would be useful if $$parms, $$vars and $$locals can
decode char pointers and print the actual strings. Right now, I get:

[root@... ~]# stap -ve 'probe kernel.function("sys_open") { printf("%s\n",
$$parms); exit()}'
Pass 1: parsed user script and 43 library script(s) in 520usr/30sys/2857real ms.
Pass 2: analyzed script: 1 probe(s), 4 function(s), 0 embed(s), 0 global(s) in
810usr/1060sys/18500real ms.
Pass 3: translated to C into
"/tmp/stapWle7r4/stap_a31159f133d564c664b654ee4b99358c_1996.c" in
490usr/460sys/1477real ms.
Pass 4: compiled C into "stap_a31159f133d564c664b654ee4b99358c_1996.ko" in
6770usr/1070sys/20445real ms.
Pass 5: starting run.
filename=0xffffffffb7fae481 flags=0x0 mode=0x1b6

Pass 5: run completed in 10usr/80sys/1525real ms.

Given the parameter name can be decoded, maybe looking at its type wouldn't be
hard. However, one needs to be careful about user_string/kernel_string. Can that
also be deciphered from the DWARF information?

Also the above was on a 32bit system... shouldn't the filename be displayed as a
32bit pointer?

-- 
           Summary: $$parms et al. should decode char *
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: ananth at in dot ibm dot com
                CC: scox at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=6837

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.