linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
	Ian McDonald <imcdnzl@gmail.com>
Subject: Re: [uml-devel] Problems with UML on Debian Sarge 64 host
Date: Thu, 14 Apr 2005 23:07:11 +0200	[thread overview]
Message-ID: <200504142307.11927.blaisorblade@yahoo.it> (raw)
In-Reply-To: <cbec11ac0504132125779afc07@mail.gmail.com>

On Thursday 14 April 2005 06:25, Ian McDonald wrote:
> Hi there,

> In my continuing saga (which some are becoming familiar with) to get
> UML 2.6.x working at all I have been given access to another machine
> to develop on and my old machine is going to disappear.

> This machine is Debian Sarge with gcc 3.3.5 on an AMD64 with 32 bit
> userspace although 64 bit compiles can also occur.

> I am doing all my UML builds with ARCH=um SUBARCH=i386 at this point in
> time.

> The problem is that my bootup dies very early on and this is the total
> output: Checking for /proc/mm...not found
> Checking PROT_EXEC mmap in /tmp...OK
> tracing thread pid = 20981
> OP_FORK failed to attach pid

> I suspect that this is something to do with my mixed 32/64 bit
> environment but I am not sure... Can anybody shed some light on this?

I've seen that *sometimes* too on 64-bit envs., tried doing a "setarch i386 
linux" or something like that, to force a 32-bit emulation?

At least sometimes it *does* make a difference.

> BTW I have also written a patch which I think is worth submitting into
> the kernel tree as it gives better debugging of error messages in
> arch/um/kernel/tt/tracer.c for where my process is dying.

> When I run with my patch it shows that it is dying on the
> PTRACE_ATTACH with an error EPERM but I can run other processes etc
> like gdb which attach to processes.
Tried disabling the ptrace proxy in compilation, as the first thing?

Remember me and I'll go merging this patchlet (it's just matter of not 
forgetting this).
> Any help would be greatly appreciated.
I hope I can help on this...
> Ian

-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2005-04-14 20:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  4:25 [uml-devel] Problems with UML on Debian Sarge 64 host Ian McDonald
2005-04-14  4:27 ` [uml-devel] " Ian McDonald
2005-04-14 21:07 ` Blaisorblade [this message]
2005-04-15  4:56   ` [uml-devel] " Ian McDonald
2005-04-19 16:05     ` Blaisorblade
2005-04-20  1:51       ` Ian McDonald
2005-04-21 15:47         ` Blaisorblade
     [not found] <CBELIFGMBIEPIEOFCJFAMEFLCAAA.brocka@sterlingcgi.com>
2005-04-17 17:32 ` Blaisorblade

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=200504142307.11927.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=imcdnzl@gmail.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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