From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31597] Systemtap not extracting all the data sent to the print data in the buffers before shutdown
Date: Wed, 17 Apr 2024 14:42:14 +0000 [thread overview]
Message-ID: <bug-31597-6586-6NkLecE3io@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31597-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31597
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
The core of the problem appears to be that when stop_threads is set any pending
data in the buffer or heap is just left there as the threads immediately exit
or at best read one more entry when stap_threads is set.
The stop_thread should act more like a "5 minutes left on the test" in college
where the read_thread_serialmode() exits either when the "5 minutes left"
expires OR there is no additional data to drain from the buffer. The
read_thread_serializer() should have similar conditions.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-04-17 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:13 [Bug runtime/31597] New: " wcohen at redhat dot com
2024-04-17 14:42 ` wcohen at redhat dot com [this message]
2024-04-26 15:56 ` [Bug runtime/31597] " wcohen at redhat dot com
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=bug-31597-6586-6NkLecE3io@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).