On Thu, May 26, 2022 at 02:30:44AM +0200, Ævar Arnfjörð Bjarmason wrote:
> `"exit"`::
> - This event is emitted when git calls `exit()`.
> + This event is emitted when git calls `exit()`. This event will
> + be produced for all regular ending of the git process, but it
> + might also exit via a "signal".
> +
The second 'this' can be elided, thus says "This event is emitted ...
and will be produced ...".
> ------------
> {
> @@ -435,7 +437,7 @@ only present on the "start" and "atexit" events.
> `"atexit"`::
> This event is emitted by the Trace2 `atexit` routine during
> final shutdown. It should be the last event emitted by the
> - process.
> + process, unless it was aborted (see "signal").
> +
Looks OK.
> @@ -452,8 +454,11 @@ completed.)
>
> `"signal"`::
> This event is emitted when the program is terminated by a user
> - signal. Depending on the platform, the signal event may
> - prevent the "atexit" event from being generated.
> + signal, which includes git itself calling abort(3). Depending
> + on the platform, the signal event may prevent the "exit"
> + and/or "atexit" events from being generated. E.g. if BUG() was
> + invoked we'll emit an "error" event followed by a "signal"
> + event, and nothing else.
> +
So in case of BUG() trigger, there may not be exit event due to user
signal right? I'm expecting system (not user) signal in that case.
--
An old man doll... just what I always wanted! - Clara
