From: Hui Zhu <teawater@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Pedro Alves <palves@redhat.com>,
Julien Desfossez <jdesfossez@efficios.com>,
lttng-dev <lttng-dev@lists.lttng.org>,
Tom Tromey <tromey@redhat.com>,
gdb@sourceware.org
Subject: Re: [lttng-dev] Request change name of function lookup_enum in libbabeltrace to make GDB use this lib
Date: Tue, 11 Dec 2012 15:19:00 -0000 [thread overview]
Message-ID: <CANFwon2T5CYcjssSyTh_yjV2fgw0N3SZXqytNJQOCR1h2vM8MQ@mail.gmail.com> (raw)
In-Reply-To: <20121210140524.GA31945@Krystal>
On Mon, Dec 10, 2012 at 10:05 PM, Mathieu Desnoyers
<mathieu.desnoyers@efficios.com> wrote:
> * Hui Zhu (teawater@gmail.com) wrote:
>> On Thu, Dec 6, 2012 at 11:57 PM, Pedro Alves <palves@redhat.com> wrote:
>> > On 12/05/2012 12:08 PM, Mathieu Desnoyers wrote:
>> >> * Hui Zhu (teawater@gmail.com) wrote:
>> >>> Hi,
>> >>>
>> >>> I am working on add CTF support to GDB. You can see my patch review threads in:
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00552.html
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00554.html
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00553.html
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00555.html
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00556.html
>> >>>
>> >>> To make GDB support CTF read, I use libbabeltrace with GDB. You can
>> >>> see the patch in
>> >>> http://sourceware.org/ml/gdb-patches/2012-11/msg00555.html.
>> >>> I have a issue is libbabeltrace have a function called lookup_enum
>> >>> that is same with a GDB function.
>> >>> I change the function name of GDB to handle this issue in my patch.
>> >>>
>> >>> But Tom said let libbabeltrace to change function name is better.
>> >>> So I send this mail to ask do you mind change the function name of
>> >>> lookup_enum? If you can change the function name that will be really
>> >>> helpful for us. Thanks a lot.
>> >>> And I post a patch about change the function name in libbabeltrace.
>> >>
>> >> I'm CCing Julien Desfossez on this one. From what I see,
>> >> include/babeltrace/types.h is not included into the system, so it should
>> >> not be considered to be a public header of libbabeltrace.
>> >
>> > I've just built and installed babeltrace 1.0.0 (where's the mainline repository,
>> > BTW?), and indeed, I'm not seeing the types.h file anywhere in the
>> > installed tree:
>> >
>> > $ ~/src/babeltrace/install/include> find
>> > .
>> > ./babeltrace
>> > ./babeltrace/trace-handle.h
>> > ./babeltrace/list.h
>> > ./babeltrace/babeltrace.h
>> > ./babeltrace/context.h
>> > ./babeltrace/iterator.h
>> > ./babeltrace/ctf
>> > ./babeltrace/ctf/callbacks.h
>> > ./babeltrace/ctf/events.h
>> > ./babeltrace/ctf/iterator.h
>> > ./babeltrace/format.h
>> > ./babeltrace/clock-types.h
>> >
>> > The GDB patch is including types.h explicitly:
>> >
>> > +#ifdef HAVE_LIBBABELTRACE
>> > +#include <babeltrace/babeltrace.h>
>> > +#include <babeltrace/types.h>
>> > +#include <babeltrace/ctf/events.h>
>> > +#include <babeltrace/ctf/iterator.h>
>> >
>> > So indeed, Hui, you'll need to make sure your patch works against an
>> > installed babeltrace, making sure it does not pick up headers
>> > from babeltrace's source directory. If there's really no reason to
>> > include that types.h header (since it seems you don't really need any
>> > function declared in that file), maybe there's actually nothing for
>> > babeltrace to do.
>>
>> Oops, sorry for I miss something.
>> I use include babeltrace/types.h because I use function
>> get_int_signedness that defined inside it.
>
> Can you use:
>
> include/babeltrace/ctf/events.h: bt_ctf_get_int_signedness() instead ?
>
> This one is within an exported header,
>
> Thanks,
>
> Mathieu
Great! My part is OK now. Thanks for your help.
Best,
Hui
>
>>
>> Thanks,
>> Hui
>>
>>
>> >
>> >> Julien, is there an publically exposed babeltrace API that performs
>> >> something similar to the internal lookup_enum() ?
>> >>
>> >> Hui, are you using other functions from include/babeltrace/types.h ?
>> >
>> > --
>> > Pedro Alves
>> >
>
> --
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
next prev parent reply other threads:[~2012-12-11 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 11:38 Hui Zhu
2012-12-05 12:08 ` [lttng-dev] " Mathieu Desnoyers
2012-12-05 12:22 ` Hui Zhu
2012-12-06 15:57 ` Pedro Alves
2012-12-06 16:21 ` Pedro Alves
2012-12-06 16:25 ` Mathieu Desnoyers
2012-12-10 8:31 ` Hui Zhu
2012-12-10 14:05 ` Mathieu Desnoyers
2012-12-11 15:19 ` Hui Zhu [this message]
2012-12-20 13:47 ` Hui Zhu
2012-12-20 14:16 ` Mathieu Desnoyers
2012-12-21 2:58 ` Hui Zhu
2013-01-07 21:19 ` Mathieu Desnoyers
2013-01-09 19:48 ` [BABELTRACE PATCH] Namespace the lookup_enum function Julien Desfossez
2013-01-13 17:58 ` Mathieu Desnoyers
2013-01-24 17:43 ` [lttng-dev] " Julien Desfossez
2013-01-25 11:17 ` Hui Zhu
2012-12-06 10:51 ` Request change name of function lookup_enum in libbabeltrace to make GDB use this lib John Gilmore
2012-12-06 12:13 ` Hui Zhu
2012-12-06 15:38 ` 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=CANFwon2T5CYcjssSyTh_yjV2fgw0N3SZXqytNJQOCR1h2vM8MQ@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb@sourceware.org \
--cc=jdesfossez@efficios.com \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=palves@redhat.com \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).