From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco] Zap mi1 reference
Date: Tue, 17 Feb 2004 19:00:00 -0000 [thread overview]
Message-ID: <403264E6.2010807@gnu.org> (raw)
In-Reply-To: <20040216234151.GA4921@white>
> If I was to write an MI module for libtgdb, do you see that working for
> only gdb 6.0? Would I then have to write a MI2 module for 6.1? I would
> hope that my MI1 library would work with both GDB 6.0,6.1. Is this a
> quality the MI protocol is going to sustain? and that an MI2 module
> would only allow for more functionality, or more of something.
>
>
>> - using frame ID's with varobj
>> - N:M breakpoints
>> will impact significantly on the MI interface.
>
>
> Will this break all MI1 front end clients?
To turn the problem around, clients that don't exploit the new
mechanisms are, by definition, already broken :-/
For instance without a frame ID it isn't possible for varobj to
correctly identify a frame. This means that when your existing code
tries to debug frameless i386 backtraces it's going to fail in wierd and
wonderful ways (typically by selecting the wrong frame). Only by by
identifying frames using a frame ID will your code be able to work robustly.
Andrew
next prev parent reply other threads:[~2004-02-17 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 20:05 Andrew Cagney
2004-02-13 20:37 ` Bob Rossi
2004-02-16 23:27 ` Andrew Cagney
2004-02-16 23:41 ` Bob Rossi
2004-02-17 19:00 ` Andrew Cagney [this message]
2004-02-14 11:34 ` Eli Zaretskii
2004-02-16 23:17 ` Andrew Cagney
2004-02-17 7:06 ` Eli Zaretskii
2004-02-17 14:55 ` Andrew Cagney
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=403264E6.2010807@gnu.org \
--to=cagney@gnu.org \
--cc=bob@brasko.net \
--cc=gdb-patches@sources.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