From: Philip Quaife <test12345678@maxnet.co.nz>
To: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Patch Gdb - target h8300 sim
Date: Sat, 30 Aug 2003 11:47:00 -0000 [thread overview]
Message-ID: <XFMail.20030830234229.test12345678@maxnet.co.nz> (raw)
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi,
I was given your email as address for patches to gdb. Please advice if you
are not the correct person.
Problem.
Gdb version 5.3 target h8300-coff. Machine h8300h. Simulator
Demonstration of fault.
set machine h8300h
target sim
Gdb Abort!
Cause of fault.
Incorrect definition of number of machine registers in tm-h8300.h
Patch
diff -c tm-h8300.h tm-h8300.h-orig
Fix is alpha as there is another definition of NUM_REGS in h8300-tdep.c ,
these two need to be merged and integrated into the gdb definitions for h8300
registers.
--
Philip Quaife
Q Solutions
[-- Attachment #2: pwq-h8300-reg.patch-tm-h8300.h --]
[-- Type: application/octet-stream, Size: 825 bytes --]
*** tm-h8300.h Sat Aug 30 23:21:43 2003
--- tm-h8300.h-orig Fri Aug 29 23:39:55 2003
***************
*** 100,112 ****
#define REGISTER_SIZE 4
! /*
! PWQ 30/8/03 - TEMPORARY PATCH for Wrong # REGS on h8300h machine
! This def is duplicated in h8300-tdep.c ,both should be merged into header
! file. Correct number is probably 12
! */
!
! #define NUM_REGS 13
#define REGISTER_BYTES (NUM_REGS * 4)
--- 100,106 ----
#define REGISTER_SIZE 4
! #define NUM_REGS 14
#define REGISTER_BYTES (NUM_REGS * 4)
***************
*** 318,321 ****
one that takes account of generic CALL_DUMMY frames */
#define GET_SAVED_REGISTER(raw_buffer, optimized, addrp, frame, regnum, lval) \
generic_unwind_get_saved_register (raw_buffer, optimized, addrp, frame, regnum, lval)
-
--- 312,314 ----
next reply other threads:[~2003-08-30 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 11:47 Philip Quaife [this message]
2003-09-02 18:47 ` 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=XFMail.20030830234229.test12345678@maxnet.co.nz \
--to=test12345678@maxnet.co.nz \
--cc=ac131313@redhat.com \
--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