Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alex Bennee <kernel-hacker@bennee.com>
To: gdb@sources.redhat.com
Subject: Summary of differences between FSF GDB and ST's Micro Connect version
Date: Tue, 18 Feb 2003 12:09:00 -0000	[thread overview]
Message-ID: <1045569787.2506.96.camel@cambridge.braddahead> (raw)

Hi,

In a naieve attempt to get my Micro Connect ICE to talk to the latest
gdb I thought I'd better have a look at the diff's between the two
sources and inquire to the list if its worth forward porting any of the
changes into the latest gdb source tree. I'm unsure if some of the arch
specific stuff had been covered in later versions.

The version of gdb that I was supplied is quite old 20020211 and has had
patches made to it by both by SuperH, Inc and ST. I've only skimmed
through the diffs (~6000 lines) so the comments are brief.

BFD Changes (bfd/)

bfd/bfd-in2.h - Added addtional SH relocation types

GDB Changes (gdb/)

Various SH specific changes to deal with breakpoints, frame handling etc
Changes to handle SH virtual registers
Changes to dwarf handling
Some code #if 0'd out to either bypass "bugs" or hardwire things for SH
cases
gdbarch updated
A fair number of explicit variable initialisations and single line
changes.

GDB CLI (gdb/cli)

New functions added:
	sleep_escape (seems to sleep for a bit)
	fork_escape (forks external process setting up some pipes) - this is
used to lauch the external gdbserver in my setup

Command file tracing added (-v).

So I guess my question is will any of these patches of been forward
ported into 5.3 or submitted by SuperH for inclusion? I know the cli
changes have not but I fear these in themselves may not be enough to get
the latest gdb working with the gdb server.

-- 
Alex, homepage: http://www.bennee.com/~alex/

SCCS, the source motel!  Programs check in and never check out!
		-- Ken Thompson


             reply	other threads:[~2003-02-18 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 12:09 Alex Bennee [this message]
2003-02-18 20:38 ` 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=1045569787.2506.96.camel@cambridge.braddahead \
    --to=kernel-hacker@bennee.com \
    --cc=gdb@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