From: Yordan Karadzhov <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] Final fixes before KS 2.0
Date: Tue, 18 May 2021 10:30:42 +0300 [thread overview]
Message-ID: <80aafcf7-2ef5-01bd-b417-626e6b10b293@gmail.com> (raw)
In-Reply-To: <20210517192104.0272eb84@gandalf.local.home>
On 18.05.21 г. 2:21, Steven Rostedt wrote:
> On Mon, 17 May 2021 17:21:33 +0300
> "Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
>
>> v2 changes:
>> - Still showing all CPU plots from the new trace file when
>> appending [PATCH kernel-shark: Preserve open graphs when
>> appending data].
>> - Setting "seq.buffer" to NULL after calling trace_seq_destroy()
>> in [PATCH kernel-shark: Fix the checking if "trace_seq" was destroyed]
>> - [PATCH kernel-shark: No slash at the end of KS_PLUGIN_INSTALL_PREFIX]
>> is new.
>
> Hi Yordan,
>
> I was playing a bit with kernelshark, and found that if I load a file and
> append one, exit, load them again, then click:
>
> File -> Sessions -> Restore Last Session
>
> It crashes.
Unfortunately I am not able to reproduce the crash. maybe it has
something to do with the particular data files you use.
>
> Looks to be something is freed and then reused, because when I ran it under
> gdb, it crashed in allocation of memory (asprintf). That usually means that
> something was freed twice, someplace else. Or freed and then used.
Is it possible to send me a backtrace of the stack?
Thanks!
Yordan
>
> -- Steve
>
next prev parent reply other threads:[~2021-05-18 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 14:21 [PATCH v2 0/7] Final fixes before KS 2.0 Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 1/7] kernel-shark: Preserve markers when appending data Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 2/7] kernel-shark: Preserve open graphs " Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 3/7] kernel-shark: Clear before loading new session Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 4/7] kernel-shark: Better handling of plugins when appending data file Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 5/7] kernel-shark: Do draw the combo point of the mark Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 6/7] kernel-shark: Fix the checking if "trace_seq" was destroyed Yordan Karadzhov (VMware)
2021-05-17 14:21 ` [PATCH v2 7/7] kernel-shark: No slash at the end of KS_PLUGIN_INSTALL_PREFIX Yordan Karadzhov (VMware)
2021-05-17 23:21 ` [PATCH v2 0/7] Final fixes before KS 2.0 Steven Rostedt
2021-05-17 23:28 ` Steven Rostedt
2021-05-18 7:30 ` Yordan Karadzhov [this message]
2021-05-18 12:46 ` Steven Rostedt
2021-05-18 12:58 ` Yordan Karadzhov
2021-05-18 13:44 ` Steven Rostedt
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=80aafcf7-2ef5-01bd-b417-626e6b10b293@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).