From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4920 invoked by alias); 15 Jan 2003 16:09:47 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4841 invoked from network); 15 Jan 2003 16:09:45 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by 209.249.29.67 with SMTP; 15 Jan 2003 16:09:45 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C8AF83EDB; Wed, 15 Jan 2003 11:09:35 -0500 (EST) Message-ID: <3E2587BF.2030203@redhat.com> Date: Wed, 15 Jan 2003 16:09:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: z8k simulator broken References: <20030115042818.GA17532@nevyn.them.org> <20030115044545.GC943@bubble.sa.bigpond.net.au> <20030115145536.GA15204@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00260.txt.bz2 > 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