This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/361: Need test for default char
- From: rearnsha at arm dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 19 Feb 2002 13:54:10 -0000
- Subject: gdb/361: Need test for default char
- Reply-to: rearnsha at arm dot com
>Number: 361
>Category: gdb
>Synopsis: Need test for default char
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Feb 19 05:58:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Richard Earnshaw
>Release: unknown-1.0
>Organization:
>Environment:
all
>Description:
I've just fixed the ARM port so that it correctly sets things
for the fact that these machines default plain char to
unsigned.
This didn't fix any of the testsuite regressions, which suggests
that we are missing a test for this
>How-To-Repeat:
Toggle the setting of TARGET_CHAR_SIGNED and observe that it
doesn't alter testsuite results.
>Fix:
Write a test that checks the behaviour of plain char on a machine
and checks that gdb's behaviour matches.
>Release-Note:
>Audit-Trail:
>Unformatted: