This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/5] Read CTF by the ctf target
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 01 Mar 2013 09:15:04 +0000
- Subject: Re: [PATCH 3/5] Read CTF by the ctf target
- References: <1361931459-3953-1-git-send-email-yao@codesourcery.com> <1361931459-3953-4-git-send-email-yao@codesourcery.com> <512F9182.3080104@redhat.com> <51305ED5.7000706@codesourcery.com>
On 03/01/2013 07:55 AM, Yao Qi wrote:
> 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,
sure
> so the problem of lookup_enum function goes away.
the question really whether including those headers is enough
to catch that the user is building against a broken babeltrace,
or whether the test should try something more.
--
Pedro Alves