Re: [PATCH 3/5] Read CTF by the ctf target

Yao Qi
2013-03-01T07:55:58Z

On 03/01/2013 01:18 AM, Pedro Alves wrote:
> We know from previous patches that the latest released
> babeltrace breaks gdb, due to the lookup_enum function. Does
> this catch that? I see namespacing fixes going into
> babeltrace as recently as last 15th. Do we know if

We are using babeltrace trunk now, so the problem of lookup_enum
function goes away.

> babeltrace's API is more or less done and close to a release?
>

I am not sure, but looks the babeltrace's APIs are quite stable. I
don't see the schedule of the next babeltrace release on its website.
However, since we start to use babeltrace in GDB, I'll keep my eyes on
it and run GDB testsuite along with babeltrace trunk to make sure
nothing is broken.

>> >+ ],[],
>> >+ [AC_MSG_RESULT([yes]); AC_DEFINE(HAVE_LIBBABELTRACE, 1, [Define if libbabeltrace is available])],
>> >+ [AC_MSG_RESULT([no]); btlibs= ; btinc= ])
>> >+ CFLAGS="$saved_CFLAGS"
>> >+fi
>> >+
>> >+# Flags needed for UST
> babeltrace
>

A copy-paste error. I'll post a updated patched soon.

--
Yao (é½å°§)