From: Milian Wolff <milian.wolff@kdab.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-perf-users@vger.kernel.org, Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: perf 6.9-1 (archlinux) crashes during recording of cycles + raw_syscalls
Date: Tue, 04 Jun 2024 22:04:42 +0200 [thread overview]
Message-ID: <7152491.mzf3CD02m1@milian-workstation> (raw)
In-Reply-To: <Zl8g1LxRCYgTSxhy@x1>
On Dienstag, 4. Juni 2024 16:12:36 MESZ Arnaldo Carvalho de Melo wrote:
> On Tue, Jun 04, 2024 at 10:50:00AM -0300, Arnaldo Carvalho de Melo wrote:
> > On Tue, Jun 04, 2024 at 01:44:18PM +0200, Milian Wolff wrote:
> > > the following command crashes perf for me, is this still an issue
> > > upstream and should I report it to arch for backporting? I cannot build
> > > the official perf/ core branch, so I am afraid I cannot test it myself
> > > there:
> > >
> > > ```
> > > sudo /usr/bin/perf record -z --call-graph dwarf -e cycles -e
> > > raw_syscalls:sys_enter ls
> > > ...
> > > [ perf record: Woken up 3 times to write data ]
> > > malloc(): invalid next size (unsorted)
> > > Aborted
> > > ```
> > > Backtrace with GDB + debuginfod:
> > > ```
> > > malloc(): invalid next size (unsorted)
> >
> > I reproduced this all the way back to 6.8, trying to bisect now, thanks
> > for the report,
>
> Can you please try with the attached and perhaps provide your Tested-by?
Works a charm, thanks
Tested-by: Milian Wolff <milian.wolff@kdab.com>
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
prev parent reply other threads:[~2024-06-04 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23879991.0LEYPuXRzz@milian-workstation>
[not found] ` <Zl8bhWfHSXxs35r2@x1>
2024-06-04 14:12 ` perf 6.9-1 (archlinux) crashes during recording of cycles + raw_syscalls Arnaldo Carvalho de Melo
2024-06-04 18:48 ` Ian Rogers
2024-06-04 19:02 ` Arnaldo Carvalho de Melo
2024-06-06 22:20 ` Namhyung Kim
2024-06-06 23:17 ` Ian Rogers
2024-06-07 18:26 ` Namhyung Kim
2024-06-04 20:04 ` Milian Wolff [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=7152491.mzf3CD02m1@milian-workstation \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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