On Fri, 2017-09-08 at 15:25 -0400, Steven Rostedt wrote:
> On Tue, 5 Sep 2017 16:57:46 -0500
> Tom Zanussi wrote:
>
> > +static char *hist_err_str;
> > +static char *last_hist_cmd;
> > +
> > +static int hist_err_alloc(void)
> > +{
> > + int ret = 0;
> > +
> > +
On Fri, 2017-09-08 at 15:25 -0400, Steven Rostedt wrote:
> On Tue, 5 Sep 2017 16:57:46 -0500
> Tom Zanussi wrote:
>
> > +static char *hist_err_str;
> > +static char *last_hist_cmd;
> > +
> > +static int hist_err_alloc(void)
> > +{
> > + int ret = 0;
> > +
> > + last_hist_cmd =
On Tue, 5 Sep 2017 16:57:46 -0500
Tom Zanussi wrote:
> +static char *hist_err_str;
> +static char *last_hist_cmd;
> +
> +static int hist_err_alloc(void)
> +{
> + int ret = 0;
> +
> + last_hist_cmd = kzalloc(MAX_FILTER_STR_VAL, GFP_KERNEL);
> + if
On Tue, 5 Sep 2017 16:57:46 -0500
Tom Zanussi wrote:
> +static char *hist_err_str;
> +static char *last_hist_cmd;
> +
> +static int hist_err_alloc(void)
> +{
> + int ret = 0;
> +
> + last_hist_cmd = kzalloc(MAX_FILTER_STR_VAL, GFP_KERNEL);
> + if (!last_hist_cmd)
> +
With the addition of variables and actions, it's become necessary to
provide more detailed error information to users about syntax errors.
Add a 'last error' facility accessible via the erroring event's 'hist'
file. Reading the hist file after an error will display more detailed
information
With the addition of variables and actions, it's become necessary to
provide more detailed error information to users about syntax errors.
Add a 'last error' facility accessible via the erroring event's 'hist'
file. Reading the hist file after an error will display more detailed
information
6 matches
Mail list logo