All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc-linux-user problem
Date: Sun, 29 Apr 2007 01:24:40 +0100	[thread overview]
Message-ID: <200704290124.40951.paul@codesourcery.com> (raw)
In-Reply-To: <20070428213912.3bc3ce6b@c1358217.kevquinn.com>

On Saturday 28 April 2007, Kevin F. Quinn wrote:
> On Sat, 28 Apr 2007 18:20:55 +0100
>
> Paul Brook <paul@codesourcery.com> wrote:
> > On Saturday 28 April 2007, Blue Swirl wrote:
> > > Hi,
> > >
> > > I'm investigating why Sparc32 user emulator breaks when linked with
> > > -lrt. It seems that other libraries also cause the problem, for
> > > example -lm -ldl -lX11 -lbfd -lslang is okay, but  -lm -ldl -lX11
> > > -lbfd -lslang -lglib-2.0 segfaults just like -lm -lrt. If just
> > > address space conflict was the issue, I'd think 12 megs libbfd
> > > would trigger the problem instead of 64k librt.
> > >
> > > Any ideas?
> >
> > I've never got this to work reliably on either x86 or amd64 hosts. I
> > get mysterious segfaults in the depths of libc. My guess is that the
> > tricks qemu uses to link itself as a shared library are confusing
> > things (possibly the TLS initialisation).
>
> I don't suppose using gcc/binutils -fPIE/-pie would achieve qemu's
> goals, thus avoiding the need to specify bespoke ld scripts?

Sort-of, maybe.

Paul

      reply	other threads:[~2007-04-29  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28  9:47 [Qemu-devel] Sparc-linux-user problem Blue Swirl
2007-04-28 17:20 ` Paul Brook
2007-04-28 20:39   ` Kevin F. Quinn
2007-04-29  0:24     ` 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=200704290124.40951.paul@codesourcery.com \
    --to=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.