Files
git/builtin
Johannes Schindelin 74fb18824c bisect: handle NULL commit in bisect_successful()
When `lookup_commit_reference_by_name()` is called to find the first bad
commit, the result is passed to `repo_format_commit_message()`
immediately, which dereferences commit without checking for NULL.

However, the commit could be NULL, even though in practice this is
unlikely because `bisect_successful()` is only called after a successful
bisect run has identified the bad commit, but the ref could still become
dangling due to a concurrent gc or repository corruption.

Pointed out by Coverity.

Assisted-by: Claude Opus 4.6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-07-10 08:13:54 -07:00
..
2026-04-10 07:58:53 -07:00
2026-07-06 15:50:21 -07:00
2025-09-29 11:40:35 -07:00
2026-07-06 15:50:19 -07:00
2026-07-06 15:50:21 -07:00
2026-05-27 14:15:44 +09:00
2026-06-15 07:42:00 -07:00
2026-05-04 10:11:17 +09:00
2026-03-23 08:33:10 -07:00
2026-03-31 20:43:14 -07:00
2026-07-06 15:50:21 -07:00
2026-07-06 15:50:23 -07:00
2026-02-20 08:13:58 -08:00
2026-03-31 20:43:14 -07:00
2026-05-06 09:48:28 +09:00
2026-04-10 07:58:53 -07:00