From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
Vladimir Prus <vladimir@codesourcery.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] Use observers to report stop events.
Date: Thu, 01 May 2008 20:11:00 -0000 [thread overview]
Message-ID: <200805012111.04430.pedro@codesourcery.com> (raw)
In-Reply-To: <20080501195758.GL22218@caradoc.them.org>
A Thursday 01 May 2008 20:57:58, Daniel Jacobowitz wrote:
> Am I correct that the cleanup for finish_command is never supposed to
> survive the function returning? It's run on error and discarded on
> normal return. So you could put the closure in a local variable,
> maybe.
>
> struct foo_closure my_closure = { &my_global, my_global };
> make_cleanup (restore_integer, &my_closure);
Humm, I notice that a cleanup is being passed around to
finish_command_continuation, but it isn't being used inside -- and
it shoud not be. With continuations per thread, and and non-stop, we
can have more than one simultaneous finish command. The cleanup
chains are not per-thread, so it is not safe to run cleanups like that.
Either we have to use some other form of cleanup in this continuation,
or revert to having exec_cleanups, but this time, per thread.
--
Pedro Alves
next prev parent reply other threads:[~2008-05-01 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 20:05 Vladimir Prus
2008-04-24 13:47 ` Vladimir Prus
2008-04-29 8:03 ` Joel Brobecker
2008-04-29 18:30 ` Vladimir Prus
2008-05-01 19:58 ` Daniel Jacobowitz
2008-05-01 20:11 ` Pedro Alves [this message]
2008-05-01 20:17 ` Vladimir Prus
2008-05-04 9:05 ` Vladimir Prus
2008-05-28 18:30 ` Vladimir Prus
2008-06-05 15:41 ` Daniel Jacobowitz
2008-06-10 11:58 ` Vladimir Prus
2008-06-10 13:21 ` Daniel Jacobowitz
2008-06-10 13:25 ` Vladimir Prus
2008-06-10 13:51 ` Daniel Jacobowitz
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=200805012111.04430.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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