From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Tom Tromey'" <tromey@redhat.com>,
"'Jan Kratochvil'" <jan.kratochvil@redhat.com>,
"'Mikhail Khodjaiants'" <mikhailkhod@googlemail.com>
Cc: "'André Pönitz'" <andre.poenitz@mathematik.tu-chemnitz.de>,
"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>,
"'Dodji Seketeli'" <dodji@redhat.com>
Subject: RE: RFC: implement "catch signal"
Date: Wed, 19 Dec 2012 20:11:00 -0000 [thread overview]
Message-ID: <E59706EF8DB1D147B15BECA3322E4BDC04C7E5@eusaamb103.ericsson.se> (raw)
In-Reply-To: <877godon2q.fsf@fleche.redhat.com>
> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com]
> Sent: Wednesday, December 19, 2012 2:32 PM
> To: Jan Kratochvil
> Cc: André Pönitz; gdb-patches@sourceware.org; Marc Khouzam;
> Dodji Seketeli
> Subject: Re: RFC: implement "catch signal"
>
> Jan> I do not know how serious is the backward compatibility of
> Jan> type="catchpoint".
>
> Tom> Me neither.
>
> On irc, André said that at least his front end isn't handling
> catchpoint
> at all. So I would guess that changing this, at least for
> him, would be
> fine.
>
> CCing Marc Khouzam, to get the Eclipse perspective, and Dodji for
> nemiver.
>
> The background is that right now all catchpoints report
> type="catchpoint" in MI; but it seems better to me to make this report
> the real catchpoint type, e.g., type="catch-load" or something like
> that.
>
> The alternative is something like type="catchpoint",catch-type="load".
Eclipse looks for 'type' to start with "catchpoint", so having something
like type="catchpoint-load" would be backwards-compatible in our case.
I've added Mikhail Khodjainants who has recently worked on synchronizing
Eclipse and GDB 'breakpoints' but ran into serious problems for catchpoints.
> I sometimes think we should have a special "MI discuss" list
> just so we
> can work these things out without requiring all the MI
> consumer authors
> to filter through the main lists. Just CCing a couple people whose
> names I remember isn't very good... :)
gdb-mi@source...
could be a good thing to have.
>
> Tom
>
next prev parent reply other threads:[~2012-12-19 20:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 19:07 Tom Tromey
2012-11-16 19:49 ` Eli Zaretskii
2012-11-17 2:22 ` Yao Qi
2012-12-02 9:38 ` Jan Kratochvil
2012-12-03 18:59 ` Tom Tromey
2012-12-03 19:37 ` Jan Kratochvil
2012-12-03 19:39 ` Tom Tromey
2012-12-03 20:22 ` André Pönitz
2012-12-03 20:31 ` Jan Kratochvil
2012-12-07 18:42 ` Tom Tromey
2012-12-07 19:28 ` Jan Kratochvil
2012-12-07 19:47 ` Tom Tromey
2012-12-07 20:04 ` Jan Kratochvil
2012-12-17 21:43 ` Tom Tromey
2012-12-18 16:39 ` Jan Kratochvil
2012-12-18 16:45 ` Tom Tromey
2012-12-18 16:50 ` Jan Kratochvil
2012-12-19 19:32 ` Tom Tromey
2012-12-19 20:11 ` Marc Khouzam [this message]
2012-12-20 8:58 ` Dodji Seketeli
2013-01-03 18:06 ` Tom Tromey
2012-12-07 18:41 ` Tom Tromey
2013-01-03 18:16 ` RFA: [1/2] add "catch-type" to all catchpoints Tom Tromey
2013-01-03 18:39 ` Eli Zaretskii
2013-01-16 17:23 ` Tom Tromey
2013-01-03 18:23 ` RFA: [2/2] catch signal Tom Tromey
2013-01-16 17:28 ` 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=E59706EF8DB1D147B15BECA3322E4BDC04C7E5@eusaamb103.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=andre.poenitz@mathematik.tu-chemnitz.de \
--cc=dodji@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mikhailkhod@googlemail.com \
--cc=tromey@redhat.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