This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Eliminate tui_command_loop
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- Cc: Pedro Alves <pedro at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Fri, 05 Aug 2011 00:48:56 -0300
- Subject: Re: Eliminate tui_command_loop
- References: <201108042110.45405.pedro@codesourcery.com> <4E3B0358.6000307@br.ibm.com>
Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
> On 08/04/2011 05:10 PM, Pedro Alves wrote:
>> which predates TRY_CATCH by a few years:
>> <http://sourceware.org/ml/gdb/2005-01/msg00064.html>
>
> Since you brought the subject: I noticed a while ago that there are some
> places which declare the exception variable used in TRY_CATCH without
> the volatile keyword. At the time I changed all such occurrences to volatile
> but there was no effect in the testsuite so I didn't bother submitting the
> patch upstream. Is this important?
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2016.html
IMHO (and if you still have this patch in hands) this is important, even
if just for keeping the standard :-).