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 1001524] New: Cortex-M: Remote 'g' packet reply is too long
Date: Wed, 07 Mar 2012 16:58:00 -0000 [thread overview]
Message-ID: <bug-1001524-13@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001524
Summary: Cortex-M: Remote 'g' packet reply is too long
Product: eCos
Version: CVS
Platform: All
OS/Version: Cortex-M
Status: NEW
Severity: enhancement
Priority: normal
Component: GDB stubs
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: john@dallaway.org.uk
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
When connecting to the Cortex-M GDB stub from recent versions of GDB, an error
is observed:
> (gdb) tar rem /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Remote 'g' packet reply is too long: e14e000810000000000000001000000000000000000000000000000000000000000000000000000000000000fccf0d6800000000e8cf0d6895680008e24e00080000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000021
> (gdb)
This occurs because the default register set for ARM M-profile targets has been
reduced (FPA registers have been removed) in recent GDB.
We should add a CDL option to the Cortex-M architectural HAL which allows the
stub to return the register set with or without the FPA registers.
--
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.
next reply other threads:[~2012-03-07 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 16:58 bugzilla-daemon [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-03-07 16:58 [Bug 1001524] New: " 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=bug-1001524-13@http.bugs.ecos.sourceware.org/ \
--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: 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).