This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
remote/1022: GDB 5.3 BUG Report for H8/300H and H8S
- From: shrinivasa at kpit dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 3 Feb 2003 05:36:44 -0000
- Subject: remote/1022: GDB 5.3 BUG Report for H8/300H and H8S
- Reply-to: shrinivasa at kpit dot com
>Number: 1022
>Category: remote
>Synopsis: GDB 5.3 BUG Report for H8/300H and H8S
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Feb 03 05:38:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: shrinivasa@kpit.com
>Release: GDB Insight 5.3
>Organization:
>Environment:
Windows
>Description:
Hi,
I am using GDB Insight 5.3.
I observed following error when writing GDB stub for H8S target using Remote/Serial connection.
Whenever I want to write to memory location beyond 64K, the GDB truncates the address to lower 16 bit of the expected address.
e.g. When I want to write to 0x40200 location the GDB sends following command $m200,34#92
Before connection I am use following commands in command window
(gdb) set debug remote 1
(gdb) set architecture h8300s
This does not happen in case of GDB 5.2.1, where the address is sent correctly.
i.e. for above example following command is sent. $m40200,34#f6
Is there any solution for this ?
Regards
Shrinivas
>How-To-Repeat:
Connect to target using Remote/Serial.
Set debug remote 1
Set architechture h8300s
Read/Write to any memory location beyond 0xFFFF.
Observe the sent command.
>Fix:
Use GDB 5.2.1. As GDB 5.2.1 forms correct command.
>Release-Note:
>Audit-Trail:
>Unformatted: