From: Andrew Cagney <ac131313@cygnus.com>
To: Christian Groessler <cpg@aladdin.de>
Cc: binutils@sources.redhat.com, GDB Discussion <gdb@sources.redhat.com>
Subject: Re: z8k fixes (GDB 5.1)
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <3AA12A41.A7F3F6A0@cygnus.com> (raw)
In-Reply-To: <87wvan0wyj.fsf@panther.aladdin.de>
> 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..)
Here broken means ``it doesn't build''. If it builds but dumps core when
you try to run it then that just means that it doesn't work very well
;-)
Using current sources I'm seeing:
*** BFD does not support target z8k-coff.
*** Look in bfd/config.bfd for supported targets.
Configure in /home/scratch/GDB/X-z8k-coff/opcodes failed, exiting.
Since src/opcodes is shared with GDB, your changes will fix this part of
GDB as well.
For GDB 5.1, I'll document the z8k as broken. If the build problems get
resolved, let the GDB group know (gdb@sources.redhat.com). The files
gdb/TODO and gdb/MAINTAINERS can then be updated to reflect that changed
reality.
> I created a z8k coff executable "hello".
> Start z8k gdb
> "target sim"
> "load hello"
> "run"
Yes, that is correct usage.
Good luck.
Andrew
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 2:49 z8k fixes Christian Groessler
2001-03-21 15:59 ` Andrew Cagney [this message]
2001-03-21 15:59 z8k fixes (GDB 5.1) Christian Groessler
2001-03-21 15:59 ` Alan Modra
2001-03-21 15:59 ` J.T. Conklin
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=3AA12A41.A7F3F6A0@cygnus.com \
--to=ac131313@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=cpg@aladdin.de \
--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).