This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: RDI target broken in 000215 snapshot

To: Fernando Nasser <fnasser at cygnus dot com>
Subject: Re: RDI target broken in 000215 snapshot
From: Grant Edwards <grante at visi dot com>
Date: Thu, 24 Feb 2000 16:18:12 -0600
Cc: Fernando Nasser <fnasser at redhat dot com>, gdb at sourceware dot cygnus dot com
References: <20000221104541.A28578@visi.com> <38B2AD14.7B0B4A4E@redhat.com> <20000224124726.A663@visi.com> <38B58292.3B11D622@cygnus.com> <20000224134607.A6354@visi.com> <38B59CE1.4CFA7F1E@cygnus.com> <20000224152638.A2092@visi.com>

On Thu, Feb 24, 2000 at 03:26:38PM -0600, Grant Edwards wrote:

> I had assumed that gdb was detecting the endianness of the
> target already (before today, I didn't know it was user
> selectable).  I'll take a look at makeing the "auto" mode pay
> attention to the target hardware indication.

Does the Angel monitor report the current hardware status
correctly?  The EPI Jeeni correctly reports my target is
big-endian, but the ARM EmbeddedICE reports that it is little.

Unless most targets correctly report correct endian status,
it's probably not worth paying attention to it.

-- 
Grant Edwards
grante@visi.com

References:
- RDI target broken in 000215 snapshot
  - From: Grant Edwards
- Re: RDI target broken in 000215 snapshot
  - From: Fernando Nasser
- Re: RDI target broken in 000215 snapshot
  - From: Grant Edwards
- Re: RDI target broken in 000215 snapshot
  - From: Fernando Nasser
- Re: RDI target broken in 000215 snapshot
  - From: Grant Edwards
- Re: RDI target broken in 000215 snapshot
  - From: Fernando Nasser
- Re: RDI target broken in 000215 snapshot
  - From: Grant Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]