This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [QUESTION] About the behavior when MAXACTION is exceeded

From: "Frank Ch. Eigler" <fche at redhat dot com>
To: Zexuan Luo <spacewanderlzx at gmail dot com>
Cc: systemtap at sourceware dot org
Date: Mon, 28 Jan 2019 22:48:56 -0500
Subject: Re: [QUESTION] About the behavior when MAXACTION is exceeded
References: <CAADJU11NvALaz+G1t96w_47PiqxLfuUT_T-pMTG12Y=1yhy2oQ@mail.gmail.com> <87tvhs5m7q.fsf@redhat.com> <CAADJU13AvczdXopt9OaTcVYHGxQM_FppGpoUfv-UvnD_-BGjGg@mail.gmail.com>

Hi -

> However, is it acceptable to optionally consider 'MAXACTION exceeded'
> as a recoverable error, and avoid aborting the script? Is there any
> side-effect to do so?

Setting -DMAXERRORS=NNN is one way of making this error non-fatal.
We don't have a flag for turning this particular error into a warning,
but would consider merging such a patch.

- FChE

References:
- [QUESTION] About the behavior when MAXACTION is exceeded
  - From: Zexuan Luo
- Re: [QUESTION] About the behavior when MAXACTION is exceeded
  - From: Frank Ch. Eigler
- Re: [QUESTION] About the behavior when MAXACTION is exceeded
  - From: Zexuan Luo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]