Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: z8k simulator broken
Date: Wed, 15 Jan 2003 16:09:00 -0000	[thread overview]
Message-ID: <3E2587BF.2030203@redhat.com> (raw)
In-Reply-To: <20030115145536.GA15204@nevyn.them.org>


> For the curious (why would you be curious?  I don't know.  I don't even
> know why I started doing this!) I don't know if this simulator was ever
> able to run GDB tests or simple newlib binaries but my guess is not
> recently.
> 
> A z8002 binary (gdb.base/break) has a .text section of size 0xeb24 or
> so.  The heap is 0x5000, the stack is 0x1000, and AFAICT a z8002 has
> only 0x10000 memory.
> 
> A z8001 has much more memory available but only in 64k segments, and
> .text is:
>   0 .text         00019a94  00000000  00000000  00000120  2**1
>                   CONTENTS, ALLOC, LOAD, CODE
> 
> i.e. much more than the one segment it can use.
> 
> 
> I was trying to multi-arch the z8k on a lark, but it's not enough of a
> lark to try to get around _that_.  Let it die.

Hmm, I'll file this one away :-)

More evidence supporting the hard-nosed requirement that someone doing a 
multi-arch must ensure that the before/after code actually works.  GDB 
isn't in the business of trying to preserve dead code.

Andrew



      reply	other threads:[~2003-01-15 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15  4:28 Daniel Jacobowitz
2003-01-15  4:46 ` Alan Modra
2003-01-15 14:55   ` Daniel Jacobowitz
2003-01-15 16:09     ` Andrew Cagney [this message]

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=3E2587BF.2030203@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.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