public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "leo at yuriev dot ru" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29438] enabling gmon for arbitrary DSO
Date: Wed, 03 Aug 2022 15:30:39 +0000	[thread overview]
Message-ID: <bug-29438-131-Jg6F1fBK1Y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29438-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29438

--- Comment #1 from Leo Yuriev <leo at yuriev dot ru> ---
I have a working draft of the patch ready, along with the tests.

However, during testing, a nasty bug was found in calculating the size of the
allocated buffer inside the `__monstartup()`, which is why `_mcount()` may
corrupt memory, and `write_call_graph()` does not output part of the collected
data (which falls outside the border).

So I'll fill one more bug with a patch, and then come back here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-03 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 20:17 [Bug libc/29438] New: " leo at yuriev dot ru
2022-08-02 20:18 ` [Bug libc/29438] " leo at yuriev dot ru
2022-08-03 15:30 ` leo at yuriev dot ru [this message]
2022-08-03 19:33 ` leo at yuriev dot ru
2022-10-21 13:39 ` nsz at gcc dot gnu.org
2023-01-30 12:32 ` leo at yuriev dot ru
2023-02-08 12:07 ` leo at yuriev dot ru
2023-02-22 22:24 ` cvs-commit at gcc dot gnu.org
2023-04-28 12:13 ` cvs-commit at gcc dot gnu.org
2023-04-28 14:35 ` cvs-commit at gcc dot gnu.org
2023-04-28 14:35 ` cvs-commit at gcc dot gnu.org
2023-04-28 17:23 ` cvs-commit at gcc dot gnu.org

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-29438-131-Jg6F1fBK1Y@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).