Project

General

Profile

Bug #223

By some reason "cpu_id =" is re-introduced as default printout

Added by Tan le tran over 8 years ago. Updated over 8 years ago.

Status:
Won't fix
Priority:
Low
Category:
-
Target version:
-
Start date:
04/25/2012
Due date:
% Done:

0%

Estimated time:

Description

Problem seen in both version of babeltrace 1.0.0-rc1 and rc2
ex:
[21:55:40.806412377] com_ericsson_......: { cpu_id = 1 }, { Sub_Name = "my string",..}

By default, babeltrace will printout "cpu_id =" string for the cpuId column.
Since this column is very obvious to detect, would it be possible to suppress the string "cpu_id =" ? If the user wants to see it, the option "-f all" can still be used.
In previous version, it used to print something like this:
ex:
[21:55:40.806412377] com_ericsson_......: { 1 }, { Sub_Name = "my string",..}

#1

Updated by Mathieu Desnoyers over 8 years ago

Issue #223 has been reported by Tan le tran.

----------------------------------------
Bug #223: By some reason "cpu_id =" is re-introduced as default printout
https://bugs.lttng.org/issues/223

Author: Tan le tran
Status: New
Priority: Low
Assignee:
Category:
Target version:

Problem seen in both version of babeltrace 1.0.0-rc1 and rc2
ex:
[21:55:40.806412377] com_ericsson_......: { cpu_id = 1 }, { Sub_Name = "my string",..}

By default, babeltrace will printout "cpu_id =" string for the cpuId column.
Since this column is very obvious to detect, would it be possible to suppress the string "cpu_id =" ? If the user wants to see it, the option "-f all" can still be used.
In previous version, it used to print something like this:
ex:
[21:55:40.806412377] com_ericsson_......: { 1 }, { Sub_Name = "my string",..}

Given basically everyone using babeltrace came up and asked me what this
"{ 1 }" meant, I really think the context field names should show up by
default. If you want to disable printout of these fields, I introduced a
babeltrace -n none (disables all field names) and there is always "-n
payload".

Thoughts ?

Thanks,

Mathieu

--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.lttng.org/my/account

--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

#2

Updated by Tan le tran over 8 years ago

The thing is that after knowing what { 1 } represents, the user no longer need to have it printed out at every single line to indicate that it is a cpu_id.

What is important to get printed out are the "labels" of each field in the payload as they change from one event to the other.

If "-n none" is used, the labels in the payload are no longer present and thus render the printout of that event not so usefull as we have to ask now what the values in the payload represent.

What if the following line is given in the help page:

By default the output will use the following output format:
[<time stamp>] (<delta time>) <provider_name>:<trace_event_name> { <cpu_id> }, { <payload_of_tracepoint> }

In this way, the user can get the explanation of { 1 } and no longer need to see { cpu_id = 1 } in the log.

What do you think ?

Regards,
Tan

#3

Updated by Tan le tran over 8 years ago

Hi Mathieu,

Please disregard this bug report.
I did not see the option "-n payload" :-(
With that option, it gives what we want to see.

Regards,
Tan

#4

Updated by Mathieu Desnoyers over 8 years ago

  • Status changed from New to Won't fix
  • Assignee set to Mathieu Desnoyers

The new behavior is OK, given that "-n payload" can be used for the old behavior.

Also available in: Atom PDF