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 13:51:00 -0000 [thread overview]
Message-ID: <4F5DFF44.5020005@redhat.com> (raw)
In-Reply-To: <1331554677-12906-1-git-send-email-yao@codesourcery.com>
On 03/12/2012 12:17 PM, Yao Qi wrote:
> Hi,
> when I am using DEF_VEC_I(int)/VEC(int) in my c code, which will be
> compiled with GDB and GDBserver, DEF_VEC_I(int) in breakpoint.h makes
> some troubles to me, because my c code has to include breakpoint.h
> indirectly when compiled for GDB, and my code either gets an error
> that VEC_int is undefined or redefined (vec.c has been moved to common/
> in my local tree).
>
> 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.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-12 13:51 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 [this message]
2012-03-12 14:14 ` Yao Qi
2012-03-12 14:45 ` Pedro Alves
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=4F5DFF44.5020005@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