Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, vladimir@codesourcery.com
Subject: need to define GDB/MI commands for Ada exception catchpoints
Date: Thu, 10 Mar 2011 12:09:00 -0000	[thread overview]
Message-ID: <20110310102009.GY30306@adacore.com> (raw)

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


             reply	other threads:[~2011-03-10 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 12:09 Joel Brobecker [this message]
2011-03-11  0:19 ` Tom Tromey

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=20110310102009.GY30306@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vladimir@codesourcery.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