Re: [PATCH v2] tracetool: also strip %l and %ll from systemtap format strings

On Wed, Jan 06, 2021 at 01:02:39PM +, Daniel P. Berrangé wrote: > All variables are 64-bit and so %l / %ll are not required, and the > latter is actually invalid: > > $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I . > parse error: invalid or missing conversion specifier > saw

Re: [PATCH v2] tracetool: also strip %l and %ll from systemtap format strings

On 1/6/21 3:36 PM, Laurent Vivier wrote: > On 06/01/2021 14:02, Daniel P. Berrangé wrote: >> All variables are 64-bit and so %l / %ll are not required, and the >> latter is actually invalid: >> >> $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I . >> parse error: invalid or missing conversion

Re: [PATCH v2] tracetool: also strip %l and %ll from systemtap format strings

On 06/01/2021 14:02, Daniel P. Berrangé wrote: > All variables are 64-bit and so %l / %ll are not required, and the > latter is actually invalid: > > $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I . > parse error: invalid or missing conversion specifier > saw: operator ',' at ./q

Re: [PATCH v2] tracetool: also strip %l and %ll from systemtap format strings

On 06/01/2021 14:02, Daniel P. Berrangé wrote: > All variables are 64-bit and so %l / %ll are not required, and the > latter is actually invalid: > > $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I . > parse error: invalid or missing conversion specifier > saw: operator ',' at ./q

[PATCH v2] tracetool: also strip %l and %ll from systemtap format strings

All variables are 64-bit and so %l / %ll are not required, and the latter is actually invalid: $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I . parse error: invalid or missing conversion specifier saw: operator ',' at ./qemu-system-x86_64-log.stp:15118:101 source: prin