public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christian Groessler <cpg@aladdin.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Christian Groessler <cpg@aladdin.de>,
	binutils@sources.redhat.com,
	GDB Discussion <gdb@sources.redhat.com>
Subject: Re: z8k fixes
Date: Mon, 19 Feb 2001 02:49:00 -0000	[thread overview]
Message-ID: <87wvan0wyj.fsf@panther.aladdin.de> (raw)

On 02/17/2001 02:03:00 AM EST Andrew Cagney wrote:
>
>Philip Blundell wrote:
>>
>> In message <87u26yxy0q.fsf@panther.aladdin.de>, Christian Groessler writes:
>> >I've got some fixes for the z8k assembler and disassembler,
>> >how can I get them integrated?
>>
>> Send the patches (preferably in `diff -up' format) to this list.
>>
>> If the changes are substantial, you will need to sign a form assigning
>> copyright to the FSF before they can be integrated.
>
>Could I also encourage you to include a GDB assignment and have a look
>at GDB.  Right now GDB's z8k support is considered broken (it doesn't
>build) and is slated for removal :-(

I tried gdb 5.0 and it compiled (at least).

Since I haven't used gdb in this way before, please let me ask
whether I used it correctly:

I created a z8k coff executable "hello".
Start z8k gdb
"target sim"
"load hello"
"run"

-> gdb segfaults

So it looks broken :-(

My binutils assignment isn't finished yet, I will try to fix binutils
first (which with my patches seem to work quite well for me).
Later I might look into gdb then (if time permits etc..)

regards,
chris

             reply	other threads:[~2001-02-19  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19  2:49 Christian Groessler [this message]
2001-03-21 15:59 ` z8k fixes (GDB 5.1) Andrew Cagney
     [not found] <E14IqGN-0000xU-00@pig.labs.futuretv.com>
2001-02-17 10:51 ` z8k fixes 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=87wvan0wyj.fsf@panther.aladdin.de \
    --to=cpg@aladdin.de \
    --cc=ac131313@cygnus.com \
    --cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).