Re: [PATCH] trace-cmd: handle NULL comm name in .dat file

2014-06-27 Thread Steven Rostedt
On Thu, 26 Jun 2014 09:22:12 -0700 Josef Bacik wrote: > Sometimes the comm field in the trace.dat file can be empty which means that > the > event parsing stuff can pass a NULL into pevent_register_comm. To fix this > just > check if we are NULL and generate a bogus comm name for that PID.

Re: [PATCH] trace-cmd: handle NULL comm name in .dat file

2014-06-27 Thread Steven Rostedt
On Thu, 26 Jun 2014 09:22:12 -0700 Josef Bacik jba...@fb.com wrote: Sometimes the comm field in the trace.dat file can be empty which means that the event parsing stuff can pass a NULL into pevent_register_comm. To fix this just check if we are NULL and generate a bogus comm name for that

[PATCH] trace-cmd: handle NULL comm name in .dat file

2014-06-26 Thread Josef Bacik
Sometimes the comm field in the trace.dat file can be empty which means that the event parsing stuff can pass a NULL into pevent_register_comm. To fix this just check if we are NULL and generate a bogus comm name for that PID. This keeps us from segfaulting. Thanks, Signed-off-by: Josef Bacik

[PATCH] trace-cmd: handle NULL comm name in .dat file

2014-06-26 Thread Josef Bacik
Sometimes the comm field in the trace.dat file can be empty which means that the event parsing stuff can pass a NULL into pevent_register_comm. To fix this just check if we are NULL and generate a bogus comm name for that PID. This keeps us from segfaulting. Thanks, Signed-off-by: Josef Bacik