From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf annotate: Fix crashes on empty annotate windows
Date: Thu, 4 Jun 2026 11:13:52 -0300 [thread overview]
Message-ID: <aiGIIBdqhFes5wJr@x1> (raw)
In-Reply-To: <aegvUXJTQT9qRoDs@google.com>
On Tue, Apr 21, 2026 at 07:15:45PM -0700, Namhyung Kim wrote:
> On Mon, Apr 20, 2026 at 12:52:17PM +0100, James Clark wrote:
> > Annotate can open with an empty window if the disassembly tool fails.
> > After the linked change, the TUI started assuming there was a current
> > annotation line and could assert or segfault in the seek, refresh, and
> > source-toggle paths.
> >
> > Handle empty annotate windows explicitly: set the asm entry count before
> > resetting the browser, return early when refreshing an empty list, and
> > ignore source line toggle when there is no current annotation line.
> >
> > Fixes the following when opening an annotation:
> >
> > perf: ui/browser.c:125: ui_browser__list_head_seek: Assertion `pos != NULL' failed.
> > Aborted
> >
> > Fixes: e201757f7a0a ("perf annotate: Fix source code annotate with objdump")
> > Assisted-by: GitHub Copilot:GPT-5.4
> > Signed-off-by: James Clark <james.clark@linaro.org>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied to perf-tools-next, for v7.2.
- Arnaldo
prev parent reply other threads:[~2026-06-04 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 11:52 [PATCH] perf annotate: Fix crashes on empty annotate windows James Clark
2026-04-22 2:15 ` Namhyung Kim
2026-05-29 9:31 ` James Clark
2026-06-04 14:13 ` Arnaldo Carvalho de Melo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aiGIIBdqhFes5wJr@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox