From: Mike Frysinger <vapier@gentoo.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim/m32c: fix memory leaks in opc2c
Date: Tue, 6 Apr 2021 18:45:22 -0400 [thread overview]
Message-ID: <YGzkgmRtollVYF1m@vapier> (raw)
In-Reply-To: <d63ac16c-3932-eecb-f456-a64acf588a7f@polymtl.ca>
On 06 Apr 2021 09:28, Simon Marchi via Gdb-patches wrote:
> On 2021-04-06 6:41 a.m., Mike Frysinger wrote:
> > On 05 Apr 2021 21:36, Simon Marchi via Gdb-patches wrote:
> >> Although I'm always in favor of using C++ for just not having to think
> >> about free-ing stuff.
> >
> > right, and we don't have to debate this :). i can let it go for the sake
> > of the gains with the better language.
> >
> > NB: this would only apply to build-time tools like opc2c.
> >
> > to be clear, if you want to take on changing these tools to C++, i'd be
> > more than happy to help review. but if you feel that's too much to take
> > on, we can do the aforementioned conditional frees.
>
> I might try to take it on as a side project, but this is clearly too big
> as an immediate solution.
that's totally understandable
> What do you think of the patch below that
> sets ASAN_OPTIONS while running the tools?
i'm not keen on pushing it in this direction exactly. it would mean every
caller would have to update & keep track.
i think you could define an IGEN variable in common/Make-common.in and change
all callers over to that. then that would be the only place you'd have to add
any sanitizer related variables to.
-mike
next prev parent reply other threads:[~2021-04-06 22:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 14:58 Simon Marchi
2021-04-05 16:23 ` Mike Frysinger
2021-04-05 18:46 ` Simon Marchi
2021-04-05 21:51 ` Mike Frysinger
2021-04-06 1:36 ` Simon Marchi
2021-04-06 10:41 ` Mike Frysinger
2021-04-06 13:28 ` Simon Marchi
2021-04-06 13:45 ` Tom Tromey
2021-04-06 18:01 ` Philippe Waroquiers
2021-04-06 22:45 ` Mike Frysinger [this message]
2021-04-07 1:45 ` Simon Marchi
2021-04-07 11:38 ` Mike Frysinger
2021-04-07 14:19 ` Simon Marchi
2021-04-08 4:51 ` Mike Frysinger
2021-04-08 13:52 ` Simon Marchi
2021-04-08 4:50 ` Mike Frysinger
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=YGzkgmRtollVYF1m@vapier \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).