From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Move catch syscall to inferior-data.
Date: Mon, 12 Mar 2012 14:45:00 -0000 [thread overview]
Message-ID: <4F5E0BEE.70702@redhat.com> (raw)
In-Reply-To: <4F5E049F.5040407@codesourcery.com>
On 03/12/2012 02:13 PM, Yao Qi wrote:
> On 03/12/2012 09:51 PM, Pedro Alves wrote:
>>>> After trying some different methods, I realize that it is not a good
>>>> way to put "DEF_VEC_I(foo)" in header file.
>>
>> Right. Just put DEF_VEC_I(int) in gdb_vecs.h and include that in
>> places that need it.
>
> Right, gdb_vecs.h can guarantee each DEF_VEC_I is included only once.
> IMO, this patch is still beneficial, because inferior.h is de-coupled
> from breakpoint.h with this patch applied.
It's never completely decoupled as other parts of inferior control
need to know about catch syscall, but, patch is okay.
--
Pedro Alves
prev parent reply other threads:[~2012-03-12 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 12:18 Yao Qi
2012-03-12 13:51 ` Pedro Alves
2012-03-12 14:14 ` Yao Qi
2012-03-12 14:45 ` Pedro Alves [this message]
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=4F5E0BEE.70702@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@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