All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	nfs@lists.sourceforge.net, bernd-schubert@gmx.de
Subject: Re: x86_64: 32bit emulation problems
Date: 1 Mar 2005 21:24:17 +0100
Date: Tue, 1 Mar 2005 21:24:17 +0100	[thread overview]
Message-ID: <20050301202417.GA40466@muc.de> (raw)
In-Reply-To: <200502282154.08009.bernd.schubert@pci.uni-heidelberg.de>

> 32bit:
> ------
> hitchcock:/home/bernd/src/tests# strace32 ./test_stat32 /mnt/test/yp
> execve("./test_stat32", ["./test_stat32", "/mnt/test/yp"], [/* 39 vars */]) = 
> 0
> uname({sys="Linux", node="hitchcock", ...}) = 0
> brk(0)                                  = 0x80ad000
> brk(0x80ce000)                          = 0x80ce000
> stat64("/mnt/test/yp", {st_mode=S_IFDIR|0755, st_size=2704, ...}) = 0

It returns 0 which is success. How can it match this code? 

	if (stat (dir, &buf) == -1)
                 fprintf(stderr, "stat for %s failed \n", dir);

It is most likely some kind of user space problem.  I would change
it to int err = stat(dir, &buf);
and then go through it with gdb and see what value err gets assigned.

I cannot see any kernel problem.

> write(2, "stat for /mnt/test/yp failed \n", 30stat for /mnt/test/yp failed 
> ) = 30
> exit_group(0)                           = ?

-Andi

  parent reply	other threads:[~2005-03-01 20:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 20:54 x86_64: 32bit emulation problems Bernd Schubert
2005-02-28 21:00 ` Bernd Schubert
2005-03-01 20:24 ` Andi Kleen [this message]
2005-03-01 21:07   ` Bernd Schubert
2005-03-01 21:07     ` Bernd Schubert
2005-03-01 21:48     ` Andi Kleen
2005-03-01 22:30       ` Bernd Schubert
2005-03-01 22:30         ` Bernd Schubert
2005-03-01 23:07         ` Andi Kleen
2005-03-01 22:10     ` Andreas Schwab
2005-03-01 22:10       ` Andreas Schwab
2005-03-01 22:19       ` Andi Kleen
2005-03-01 23:22         ` Andreas Schwab
2005-03-01 23:22           ` Andreas Schwab
2005-03-01 23:19       ` Bernd Schubert
2005-03-01 23:39         ` Andreas Schwab
2005-03-01 23:39           ` Andreas Schwab
2005-03-01 23:46         ` Andreas Schwab
2005-03-01 23:46           ` Andreas Schwab
2005-03-02  8:18           ` Andi Kleen
2005-03-02  9:13             ` Trond Myklebust
2005-03-02 11:33               ` Bernd Schubert
2005-03-02 16:53                 ` Trond Myklebust
2005-03-02 18:14                   ` Bernd Schubert
2005-03-03  9:19                   ` Andi Kleen
2005-03-03 21:16                     ` Bernd Schubert
2005-03-03 21:32                       ` Andi Kleen
2005-03-03 21:37                     ` Trond Myklebust
2005-03-03 21:46                       ` Andi Kleen
2005-03-03 22:21                         ` Trond Myklebust
2005-03-03  9:12               ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-02-28 21:08 Bernd Schubert
2005-02-28 22:26 ` Trond Myklebust
2005-02-28 23:14   ` Bernd Schubert
2005-02-28 23:43   ` Bernd Schubert
2005-03-01  0:47 ` Dan Stromberg

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=20050301202417.GA40466@muc.de \
    --to=ak@muc.de \
    --cc=bernd-schubert@gmx.de \
    --cc=bernd.schubert@pci.uni-heidelberg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@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 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.