public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001524] Cortex-M: Remote 'g' packet reply is too long
Date: Wed, 11 Apr 2012 21:05:00 -0000	[thread overview]
Message-ID: <20120411210442.7D2162F78003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001524-777@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=1001524

--- Comment #17 from Ilija Kocho <ilijak@siva.com.mk> 2012-04-11 22:04:32 BST ---
(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #12)
> > > 
> > > Well my statement was little bit too general. It's actually "C/C++GDB Hardware
> > > Debugging" plugin that comes bundled with (some configurations of) Eclipse CDT.
> > > When I tried to debug with Eclipse I got /Remote 'g' packet reply is too long:/
> > > and this was the best explanation.
> > > 
> > > Now I got old good Zylin plugin, where I can manually set commands, and it
> > > works for me (and confirms my doubt about the other one).
> > > 
> > > What matters, it's a non-issue for your GDB patch.
> > 
> > Okay. So just to be absolutely clear, do you think you have tested GDB enough
> > that I should go ahead and submit this patch to upstream GDB? Or should I wait
> > a bit longer?
> 
> Please hold on. My stub is still less then perfect so I can't confirm 100%
> functionality (please see issues below). I hope to fix it in a couple of days.

Jifl

Now I can pretty much confirm the patch. I have fixed the stub (Bug 1001558)
and now I can see all registers updated.

Ilija

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


  parent reply	other threads:[~2012-04-11 21:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 16:58 [Bug 1001524] New: " bugzilla-daemon
2012-03-07 17:04 ` [Bug 1001524] " bugzilla-daemon
2012-03-08  8:01 ` bugzilla-daemon
2012-03-09  3:59 ` bugzilla-daemon
2012-03-09  4:30 ` bugzilla-daemon
2012-03-09  9:18 ` bugzilla-daemon
2012-03-09 17:15 ` bugzilla-daemon
2012-03-10 19:01 ` bugzilla-daemon
2012-03-11  0:59 ` bugzilla-daemon
2012-03-11 13:07 ` bugzilla-daemon
2012-03-11 17:22 ` bugzilla-daemon
2012-03-30 15:54 ` bugzilla-daemon
2012-04-01 11:36 ` bugzilla-daemon
2012-04-02 20:50 ` bugzilla-daemon
2012-04-02 22:18 ` bugzilla-daemon
2012-04-02 23:37 ` bugzilla-daemon
2012-04-04 19:46 ` bugzilla-daemon
2012-04-11 21:05 ` bugzilla-daemon [this message]
2012-04-11 21:25 ` bugzilla-daemon
2012-04-12 17:44 ` bugzilla-daemon
2012-04-19  7:12 ` bugzilla-daemon
2012-04-19 15:14 ` bugzilla-daemon
2012-04-26 15:30 ` bugzilla-daemon
2012-04-26 15:33 ` bugzilla-daemon
2012-06-03 13:57 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2012-03-07 16:58 [Bug 1001524] New: " bugzilla-daemon
2012-03-07 17:04 ` [Bug 1001524] " bugzilla-daemon
2012-03-08  8:01 ` bugzilla-daemon
2012-03-09  3:59 ` bugzilla-daemon
2012-03-09  4:30 ` bugzilla-daemon
2012-03-09  9:18 ` bugzilla-daemon
2012-03-09 17:15 ` bugzilla-daemon
2012-03-10 19:01 ` bugzilla-daemon
2012-03-11  0:59 ` bugzilla-daemon
2012-03-11 13:07 ` bugzilla-daemon
2012-03-11 17:22 ` bugzilla-daemon
2012-03-30 15:54 ` bugzilla-daemon
2012-04-01 11:36 ` bugzilla-daemon
2012-04-02 20:50 ` bugzilla-daemon
2012-04-02 22:18 ` bugzilla-daemon
2012-04-02 23:37 ` bugzilla-daemon
2012-04-04 19:46 ` bugzilla-daemon
2012-04-11 21:05 ` bugzilla-daemon
2012-04-11 21:25 ` bugzilla-daemon
2012-04-12 17:44 ` bugzilla-daemon
2012-04-19  7:13 ` bugzilla-daemon
2012-04-19 15:14 ` bugzilla-daemon
2012-04-26 15:29 ` bugzilla-daemon
2012-04-26 15:33 ` bugzilla-daemon
2012-06-03 13:57 ` bugzilla-daemon

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=20120411210442.7D2162F78003@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=unassigned@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).