qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Dylan <364481568@qq.com>
Subject: Re: [Qemu-devel] how to run a application compiled for sparc platform using qemu-sparc?
Date: Thu, 9 Feb 2012 12:18:48 +0000	[thread overview]
Message-ID: <201202091218.48810.paul@codesourcery.com> (raw)
In-Reply-To: <tencent_23F2CCBF27C2E839628E6EAC@qq.com>

>  the results of readelf -l hello are as follow:
>  program headers:
>      TYPE       offset    virtAddr               phyAddr           FileSiz 
>        MemSiz LOAD      0x054    0x4000 0000       0x4000 0000    0x02bf0 
>     0x02bf0

Clearly not a linux binary.  Those have file offsets and virtual addresses 
aligned modulo page size so that they can be mmapped directly into the process 
address space.  I'm pretty sure this would fail in the same way on a real 
sparc-linux system.

Paul

      reply	other threads:[~2012-02-09 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  6:25 [Qemu-devel] how to run a application compiled for sparc platform using qemu-sparc? Dylan
2012-02-09 12:18 ` Paul Brook [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=201202091218.48810.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=364481568@qq.com \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).