public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30114] Add valgrind annotations to obstack
Date: Fri, 15 Sep 2023 15:55:37 +0000	[thread overview]
Message-ID: <bug-30114-4717-6HNrzbPw6Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30114-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Simon Marchi from comment #3)

> I suppose you are talking about:

Yes, thanks for the link.

It would also be good to instrument objalloc, which is used by BFD.
For that one, maybe in the sanitizer case, every allocation could
just be done in a new chunk.

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

      parent reply	other threads:[~2023-09-15 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 17:07 [Bug build/30114] New: " tromey at sourceware dot org
2023-02-12  2:56 ` [Bug build/30114] " sam at gentoo dot org
2023-02-12 14:41 ` tromey at sourceware dot org
2023-09-15 13:52 ` tromey at sourceware dot org
2023-09-15 13:54 ` simon.marchi at polymtl dot ca
2023-09-15 15:55 ` tromey at sourceware dot org [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=bug-30114-4717-6HNrzbPw6Z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).