This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [RFC] Remove START_INFERIOR_TRAPS_EXPECTED macro from nm header
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'Pedro Alves'" <pedro at codesourcery dot com>, <gdb-patches at sourceware dot org>
- Date: Tue, 22 Mar 2011 10:37:41 +0100
- Subject: RE: [RFC] Remove START_INFERIOR_TRAPS_EXPECTED macro from nm header
- References: <003e01cbe825$321015a0$963040e0$@muller@ics-cnrs.unistra.fr> <201103220934.26493.pedro@codesourcery.com>
> -----Message d'origine-----
> De?: Pedro Alves [mailto:pedro@codesourcery.com]
> Envoyé?: mardi 22 mars 2011 10:34
> À?: gdb-patches@sourceware.org
> Cc?: Pierre Muller
> Objet?: Re: [RFC] Remove START_INFERIOR_TRAPS_EXPECTED macro from nm
> header
>
> Why's this any better? I claim that it's worse.
> START_INFERIOR_TRAPS_EXPECTED isn't ever used by anything
> outside of the native target backend implementation ---
> it doesn't qualify in the set of macros that are evil for
> a multi-arch gdb. Then, nothing in common code _should_
> know about how many internal traps are expected
> during startup_inferior, but you've just exposed that
> detail with to_start_inferior_traps_expected.
That shows that I still didn't understand what target_ops really is:
Is there only one single target_ops that this
only for the native configuration?
If this is the case, I agree with your analysis, but
I am still not sure about that...
Pierre