public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <djiang@mvista.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: x86_64 frame pointer via thread context
Date: Mon, 08 Aug 2005 10:27:49 -0700	[thread overview]
Message-ID: <42F79615.3000108@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508080912380.18088@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>>Am I doing something wrong, or is this intended to be this way on
>>>x86_64, or is something incorrect in the kernel? This method works
>>>fine on i386. Thanks for any help!
>>
>>I just tested your program on SLES9 with updated kernel and RBP
>>looks correct to me. Probably something is wrong with your user space
>>includes or your compiler.
> 
> 
> Note that there is -fomit-frame-pointer which might give different results 
> than without the option (or explicitly -fno-omit-frame-pointer).
> 
> 
> Jan Engelhardt

I had somebody else test it on FC4 and he observed the same issue. It 
may be timing sensitive? Both platforms tested are em64t based so I'm 
not sure if on amd64 platforms it varies or not.....

And you definitely have to include the -fno-omit-frame-pointer. x86_64 
gcc by default has -fomit-frame-pointer on and without explicitly 
stating that you want frame pointer you won't get it in rBP.

It is possible that userspace or toolchain may be suspect, However, why 
is the value bad in kernel space when rBP from pt_regs is dumped?


-- 
Dave

------------------------------------------------------
Dave Jiang
Software Engineer          Phone: (480) 517-0372
MontaVista Software, Inc.    Fax: (480) 517-0262
2141 E Broadway Rd, St 108   Web: www.mvista.com
Tempe, AZ  85282          mailto:djiang@mvista.com
------------------------------------------------------


  reply	other threads:[~2005-08-08 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42F3EC97.2060906@mvista.com.suse.lists.linux.kernel>
2005-08-06 11:54 ` x86_64 frame pointer via thread context Andi Kleen
2005-08-08  7:13   ` Jan Engelhardt
2005-08-08 17:27     ` Dave Jiang [this message]
2005-08-08 17:35       ` Dave Jiang
2005-08-08 18:35   ` Dave Jiang
2005-08-08 20:06     ` Petr Vandrovec
2005-08-08 20:19       ` Dave Jiang
2005-08-08 20:27         ` Petr Vandrovec
2005-08-08 21:09           ` Dave Jiang
2005-08-08 22:29             ` Petr Vandrovec
2005-08-05 22:47 Dave Jiang

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=42F79615.3000108@mvista.com \
    --to=djiang@mvista.com \
    --cc=ak@suse.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.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