Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: cgf@cygnus.com
Cc: jimb@cygnus.com, eliz@gnu.org, jtc@redbacknetworks.com,
	jkj@sco.com, hjl@valinux.com, gdb@sourceware.cygnus.com
Subject: Re: i386: Are we settled?
Date: Sat, 13 Nov 1999 10:40:00 -0000	[thread overview]
Message-ID: <199911131839.TAA26158@delius.kettenis.local> (raw)
In-Reply-To: <19991108205721.A1683@cygnus.com>

   Date: Mon, 8 Nov 1999 20:57:21 -0500
   From: Chris Faylor <cgf@cygnus.com>
   Cc: Mark Kettenis <kettenis@wins.uva.nl>, Eli Zaretskii <eliz@gnu.org>,
	   "J. T. Conklin" <jtc@redbacknetworks.com>,
	   "J. Kean Johnston" <jkj@sco.com>, "H. J. Lu" <hjl@valinux.com>,
	   gdb@sourceware.cygnus.com
   Content-Type: text/plain; charset=us-ascii

   On Mon, Nov 08, 1999 at 08:34:08PM -0500, Jim Blandy wrote:
   >
   >> >- What format should the output from "info float" take?  (Actually, it
   >> >  sounds like this is pretty much resolved.)
   >> 
   >> Did we resolve that there would be a generic routine for displaying the
   >> stuff from "info float"?
   >
   >Yep.  Mark has written an implementation.  There have been comments
   >and suggestions, but no major objections.  I think there are copyright
   >issues to be resolved.

   Ah, that's right.  I remember seeing this now.

I just sent a new patch that implements the generic `info float'
implementation to gdb-patches.  Once it is checked in, people using
the new register layout can remove the (re)definition of FLOAT_INFO
from their `tm-xxx.h' files and remove the old code.

Mark
From steveo@world.std.com Sat Nov 13 14:25:00 1999
From: "Steven W. Orr" <steveo@world.std.com>
To: GDB <gdb@sourceware.cygnus.com>
Subject: GDB/BDM/M68K?
Date: Sat, 13 Nov 1999 14:25:00 -0000
Message-id: <Pine.LNX.4.10.9911131721040.1604-100000@localhost.localdomain>
X-SW-Source: 1999-q4/msg00263.html
Content-length: 882

We are having a devil of a time getting gdb to work with our embedded m68k 
processor. We have 4.18 gdb and a server that can either be Solaris or
Linux. Our problem has been getting a suitable stub to run on the board
side.

Yesterday, somebody suggested that maybe what we should do is see if
someone has gotten some sort of BDM solution to work.

1. Has anyone gotten this to work?
2. Can gdb talk to the board using a parallel port or are we required to
   go through a serial port?

This would be much appreciated since it would totally solve the stub side
of the problem.

TIA

-- 
-Time flies like the wind. Fruit flies like a banana. steveo@world.std.com-
-Stranger things have happened but none stranger than this. Steven W. Orr-
Does your driver's license say Organ Donor?Black holes are where God \
-------divided by zero. Listen to me! We are all individuals!---------


           reply	other threads:[~1999-11-13 10:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <19991108205721.A1683@cygnus.com>]

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=199911131839.TAA26158@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=cgf@cygnus.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@valinux.com \
    --cc=jimb@cygnus.com \
    --cc=jkj@sco.com \
    --cc=jtc@redbacknetworks.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