From: "Blue Swirl" <blauwirbel@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: uClibc <uclibc@uclibc.org>,
qemu-devel@nongnu.org, detaolb-devel@lists.sourceforge.net
Subject: Re: [Qemu-devel] ANN: DetaolB v0.4 is released
Date: Wed, 11 Jul 2007 14:17:28 +0300 [thread overview]
Message-ID: <f43fc5580707110417k402822c0g5c134e397a00769b@mail.gmail.com> (raw)
In-Reply-To: <200707101542.25709.rob@landley.net>
On 7/10/07, Rob Landley <rob@landley.net> wrote:
> On Tuesday 10 July 2007 14:30:38 Blue Swirl wrote:
> > > The sparc platform has a problem that if I boot with init as a "hello
> > > world" program everything behaves as expected (there are two in the image
> > > for testing purposes, /tools/bin/hello-dynamic and
> > > /tools/bin/hello-static). But if you boot with init=/tools/bin/bash it
> > > hangs. And so do the busybox shells.
> >
> > I think there is a problem with the dynamic loader, I get a bus error
> > when running the programs on real Sparc.
>
> Huh. That's odd because hello-dynamic is using the dynamic loader. (That's
> why there's a hello-dynamic and a hello-static.)
>
> It's entirely possibly that qemu and real sparc hardware are behaving
> differently, but I'm not seeing this bus error under qemu. (I haven't got
> real sparc hardware, so I can only debug against qemu...)
Right. Debugging the problem I found out that in Qemu, 64-bit loads
and stores to unaligned addresses do not trigger any traps as they
should. I'll commit a fix soon. The problem is in uClibc ldso, there
is this kind of store.
Running the program on qemu-sparc reveals another problem, probably
because of these definitions in ldso/ldso/sparc/dl-sysdep.h:
/* 4096 bytes alignment */
/* ...but 8192 is required for mmap() on sparc64 kernel */
#define PAGE_ALIGN 0xffffe000
#define ADDR_ALIGN 0x1fff
#define OFFS_ALIGN 0x7fffe000
On Sparc32 the correct page alignment is still 4096. Because of these
definitions, some code apparently tries to clear a 8k page, but only
4k of memory is mapped.
next prev parent reply other threads:[~2007-07-11 11:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 23:58 [Qemu-devel] ANN: DetaolB v0.4 is released Christian MICHON
2007-06-30 7:47 ` Blue Swirl
2007-06-30 10:36 ` Johannes Schindelin
2007-06-30 10:51 ` Thiemo Seufer
2007-06-30 12:07 ` Christian MICHON
2007-06-30 17:15 ` Blue Swirl
2007-07-10 17:34 ` Rob Landley
2007-07-10 18:30 ` Blue Swirl
2007-07-10 19:42 ` Rob Landley
2007-07-11 11:17 ` Blue Swirl [this message]
2007-07-11 13:34 ` [Detaolb-devel] " Christian MICHON
2007-07-11 14:20 ` Christian MICHON
2007-07-11 17:33 ` Rob Landley
2007-07-11 20:20 ` Christian MICHON
2007-07-11 17:38 ` Rob Landley
2007-07-11 20:26 ` [Detaolb-devel] " Christian MICHON
2007-06-30 12:10 ` Christian MICHON
2007-07-04 18:30 ` Christian MICHON
2007-07-04 18:54 ` Blue Swirl
2007-07-04 19:45 ` Christian MICHON
2007-07-04 20:18 ` Blue Swirl
2007-07-04 20:30 ` Christian MICHON
2007-07-04 20:52 ` Blue Swirl
2007-07-04 21:04 ` Christian MICHON
2007-07-05 12:41 ` Christian MICHON
2007-07-04 20:25 ` Andreas Färber
2007-07-04 20:32 ` Christian MICHON
2007-07-06 15:07 ` Rob Landley
2007-07-04 19:50 ` Cedric Hombourger
2007-07-04 19:54 ` Cedric Hombourger
2007-07-10 20:32 ` Bernhard Fischer
2007-07-10 20:36 ` Christian MICHON
2007-07-04 20:11 ` Christian MICHON
2007-07-05 19:23 ` Rob Landley
2007-07-05 20:28 ` Christian MICHON
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=f43fc5580707110417k402822c0g5c134e397a00769b@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=detaolb-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
--cc=uclibc@uclibc.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).