From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1172 invoked by alias); 10 Mar 2011 10:20:25 -0000 Received: (qmail 1158 invoked by uid 22791); 10 Mar 2011 10:20:25 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Mar 2011 10:20:18 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EC07A2BB06C; Thu, 10 Mar 2011 05:20:16 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id p+eMrDyV2zI7; Thu, 10 Mar 2011 05:20:16 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 79F0C2BB036; Thu, 10 Mar 2011 05:20:16 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 893261459AD; Thu, 10 Mar 2011 14:20:09 +0400 (RET) Date: Thu, 10 Mar 2011 12:09:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org, vladimir@codesourcery.com Subject: need to define GDB/MI commands for Ada exception catchpoints Message-ID: <20110310102009.GY30306@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00632.txt.bz2 While discussing the MI output for Ada exception catchpoint hits, I was wondering if we shouldn't just implement the MI equivalent of our "catch exception" commands. We have several commands: - catch exception [EXCEPTION_NAME] If used with a parameter, stop only when EXCEPTION_NAME is raised. Otherwise stop when any exception is raised. - catch exception unhandled Stop only if an unhandled exception is raised (thus eventually causing the termination of the task). - catch assert Stop if an assertion failure exception is raised. There are other catch comments, and I am not sure that we have implemented the MI equivalent on any of them. I couldn't find the equivalent of "catch catch" or "catch throw", for instance. Do we want to implement one MI command for all, or on MI command for each type of catchpoint? As far as the Ada side is concerned, I don't see a reason either way. The most native design is just to have a 1:1 mapping between the CLI command and the GDB/MI command, thus I'm proposing (adding Ada in the name to make it clearer): -catch-ada-exception [EXCEPTION_NAME] -catch-unhandled-ada-exception -catch-ada-assert There is no "prior art" that might compel us to choose certain names or solutions in order to help compatibility, so we can do whatever we think is best. WDYT? Thank you, -- Joel