public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001614] eCos GDB stub "detach" reply confusing with GDB 7.4.1 Date: Sat, 30 Jun 2012 23:09:00 -0000 [thread overview] Message-ID: <20120630230859.C227F2F78007@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001614-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001614 --- Comment #6 from Jonathan Larmour <jifl@ecoscentric.com> 2012-07-01 00:08:55 BST --- Created an attachment (id=1810) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1810) Patch to remove 'detach' support (In reply to comment #5) > > Someone, way back, decided that the eCos GDB stub should do _something_ with > detach requests rather than nothing at all. As I mentioned before, my assumption for the rationale has been that it was thought better to return to a ROM monitor (which, given Mark made this change, would have been in the context of CygMon!) than just remain stuck in the stub. As I said before this rationale is arguable. That doesn't make it right. > The processing of 'D' packets was > explicitly added to the stub 2001-08-24. It does seem strange to me that we > currently issue an empty reply (indicating that the command is not supported) > but then we go ahead and do something anyway (albeit with modified semantics). > > I agree that it would be preferable to implement correct detach semantics. I > also agree that this not necessarily high priority. In the meantime, replying > "OK" ("I'm going to do something") still seems more correct to me than replying > with an empty string ("I'm ignoring this"). But OK doesn't mean "I'm going to do something", it means "I'm going to detach". But it doesn't do that. So again, can you clarify what purpose you have for wanting to use detach, since given the patch, you would want it to be doing something which is more accurately served by 'kill'. There are other GDB features that can't be properly supported by eCos, such as inferior function calling - we don't promise to support everything GDB provides just because GDB provides it. So personally, I would be equally happy to remove 'D' packet support as implement detach support. All that's needed is the attached patch. If no-one needs detach semantics, then we should remove it as it doesn't match the documented behaviour. Then GDB will return "Remote doesn't know how to detach" and everything will be consistent with documented behaviour. But it depends on why you wanted to use detach in the first place. Jifl -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
prev parent reply other threads:[~2012-06-30 23:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-24 16:43 [Bug 1001614] New: eCos GDB stub "detach" reply incompatible " bugzilla-daemon 2012-06-24 16:49 ` [Bug 1001614] " bugzilla-daemon 2012-06-25 12:29 ` bugzilla-daemon 2012-06-25 13:41 ` bugzilla-daemon 2012-06-25 14:46 ` bugzilla-daemon 2012-06-30 16:44 ` [Bug 1001614] eCos GDB stub "detach" reply confusing " bugzilla-daemon 2012-06-30 23:09 ` bugzilla-daemon [this message]
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=20120630230859.C227F2F78007@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).