Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Assert leftover cleanups in TRY_CATCH
Date: Tue, 07 May 2013 14:40:00 -0000	[thread overview]
Message-ID: <87ip2uvonz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130507062305.GH5278@adacore.com> (Joel Brobecker's message of	"Tue, 7 May 2013 10:23:05 +0400")

Joel> Should we consider changing it into an internal_warning?

I think that is fine as long as it still makes tests fail.

Tom> I think it would be possible to automate adding this declaration in
Tom> all needed spots.  I'm curious what you think about it.

Joel> I'm certainly curious about the suggestion. How would the current
Joel> code be adapted to make this work?

Well, first a manual patch both to define this macro appropriately and
to add whatever supporting functions are needed.

Then, modify the cleanup checker to add this declaration to any function
it thinks could use it.  The cleanup checker already has some code,
written in a more optimistic time, to try to determine whether a
function could be converted to "RAII style".  It could be adapted to
insert the macro use at the right spot.

Then, rebuild and fix whatever bugs were introduced.

Finally, update our patch review guidelines so we know to look for this
macro in ordinary cleanup-using functions.


Alternatively I think we could probably change all the code to be
cleanup-checker-clean.  I'll try to prep that series soon to see what
people think.  I think it actually less work.

Tom


  parent reply	other threads:[~2013-05-07 14:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 16:57 Jan Kratochvil
2013-05-02 17:02 ` Pedro Alves
2013-05-05 16:56   ` [commit] " Jan Kratochvil
2013-05-06 17:57 ` Tom Tromey
2013-05-06 18:18   ` Jan Kratochvil
2013-05-06 18:50     ` Tom Tromey
2013-05-07  1:47       ` Jan Kratochvil
2013-05-07  4:37         ` Doug Evans
2013-05-07  4:49           ` Doug Evans
2013-05-07 15:24           ` Jan Kratochvil
2013-05-15  0:13             ` Benchmarking (was Re: [patch 2/2] Assert leftover cleanups in TRY_CATCH) Stan Shebs
2013-05-15 17:00               ` Doug Evans
2013-05-22 20:51                 ` Tom Tromey
2013-05-07 14:36         ` [patch 2/2] Assert leftover cleanups in TRY_CATCH Tom Tromey
2013-05-07 18:00           ` Jan Kratochvil
2013-05-07  6:23   ` Joel Brobecker
2013-05-07 14:20     ` [patch] " Jan Kratochvil
2013-05-14 20:39       ` [commit] " Jan Kratochvil
2013-05-07 14:40     ` Tom Tromey [this message]
2013-05-07 14:55       ` Jan Kratochvil
2013-05-07 15:26       ` Tom Tromey
2013-05-08  5:54       ` Joel Brobecker

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=87ip2uvonz.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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