From: "Gene Kozin" <gkozin@c-cube.com>
To: "eCos Mailing List" <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Alert: SPARClite gdb bux (and fix)
Date: Thu, 08 Jul 1999 11:29:00 -0000 [thread overview]
Message-ID: <005101bec96f$de410af0$1d041eac@ccube.com> (raw)
The following bug has been found in SPARClite gdb from the
99-03-19 release of eCos tools (ecosSWtools-990319):
Description:
-----------
When connecting to Fujitsu SPARClite evaluation board, gdb
aborts with the following error message: "Magic number of
sparclite target struct wrong".
The said error message is emitted by the function
push_target() (target.c, line 523) if verification of the
target_ops structure fails. The failure occurs when
function sparclite_open() calls push_target() with
&sparclite_ops as an argument (see sparcl-tdep.c, line 508).
This happens because initialization of the sparclite_ops
structure (see sparcl-tdep.c, line 836) is incorrect.
Particularly, initialization of the to_has_thread_control
field (see target.h, line 318) is missing. As a result,
OPS_MAGIC (3840) ends up in the wrong field
(to_sections_end instead of to_magic), causing push_target()
to fail.
How to repeat:
--------------
1. Run sparclite-elf-gdb
2. Connect to the Fujitsu evaluation board:
(gdb) target sparclite com2
3. gdb aborts with to following message:
[SPARClite appears to be alive]
Magic number of sparclite target struct wrong
How to fix:
-----------
To fix the problem, apply the following patch to
.../src/gdb/sparcl-tdep.c file:
-----< patch-start >----------------------
876d875
< 0, /* to_has_thread_control */
-----< patch-end >------------------------
next reply other threads:[~1999-07-08 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-08 11:29 Gene Kozin [this message]
1999-07-08 11:42 ` Stan Shebs
1999-07-09 8:30 ` [ECOS] Re: ecos/20273 " Hugo Tyson
1999-07-09 11:33 ` Gene Kozin
1999-07-12 4:15 ` Hugo Tyson
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='005101bec96f$de410af0$1d041eac@ccube.com' \
--to=gkozin@c-cube.com \
--cc=ecos-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).