From: Simon Marchi <simon.marchi@polymtl.ca>
To: Michael Weghorn <m.weghorn@posteo.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH v5 1/2] gdbsupport: allow to specify dependencies between observers
Date: Mon, 26 Apr 2021 18:18:54 -0400 [thread overview]
Message-ID: <1e4e65d0-14dd-fd20-3d81-9c0b5b5da0ec@polymtl.ca> (raw)
In-Reply-To: <8f7047ef-372f-36de-b87a-03fceb198bb7@posteo.de>
On 2021-04-26 3:56 p.m., Michael Weghorn wrote:
> On 26/04/2021 16.53, Simon Marchi wrote:
>> From: Michael Weghorn <m.weghorn@posteo.de>
>>
>> Previously, the observers attached to an observable were always notified
>> in the order in which they had been attached. That order is not easily
>> controlled, because observers are typically attached in _initialize_*
>> functions, we are called in an undefined order.
>
> Just a nit-pick, should that read "functions, WHICH are called in an undefined order."?
Yes, thanks for spotting that.
Simon
next prev parent reply other threads:[~2021-04-26 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 14:53 [PATCH v5 0/2] Make sure autoload happens before notifying Python side in new_objfile event Simon Marchi
2021-04-26 14:53 ` [PATCH v5 1/2] gdbsupport: allow to specify dependencies between observers Simon Marchi
2021-04-26 19:56 ` Michael Weghorn
2021-04-26 22:18 ` Simon Marchi [this message]
2021-04-27 8:30 ` Andrew Burgess
2021-04-27 13:34 ` Simon Marchi
2021-04-26 14:53 ` [PATCH v5 2/2] gdb: do autoload before notifying Python side in new_objfile event Simon Marchi
2021-04-26 19:56 ` Michael Weghorn
2021-04-26 20:44 ` Simon Marchi
2021-04-27 8:39 ` Andrew Burgess
2021-04-27 13:43 ` Simon Marchi
2021-04-27 13:53 ` Simon Marchi
2021-04-29 15:39 ` Vaseeharan Vinayagamoorthy
2021-04-29 19:41 ` Michael Weghorn
2021-04-29 19:47 ` Simon Marchi
2021-04-26 20:05 ` [PATCH v5 0/2] Make sure autoload happens " Michael Weghorn
2021-04-27 15:23 ` Simon Marchi
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=1e4e65d0-14dd-fd20-3d81-9c0b5b5da0ec@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=m.weghorn@posteo.de \
/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).